PhotoPrism® is an AI-powered, privacy-first app for
browsing, organizing, and sharing photos and videos. It helps tag,
search, and rediscover media without getting in your way, whether
self-hosted or in the cloud.
To get a first impression, you are welcome to play with our public demo. Please be careful not to upload any private, unlawful or offensive pictures.
Feature Overview
Our mission is to provide the most user- and privacy-friendly solution to keep your pictures organized and accessible.
That's why PhotoPrism was built from the ground up to run wherever you
need it, without compromising freedom, privacy, or functionality:
Whether you're using a phone, tablet, or desktop computer, our intuitive PWA provides a native app-like experience and can be easily installed on your home screen
Being completely self-funded and independent, we can promise you that we will never sell your data and that we will always be transparent
about our software and services. Your data will never be shared with
Google, Amazon, Microsoft or Apple unless you intentionally upload files
to one of their services. 🔒
Your continued support helps us provide regular updates and remain
independent, so we can fulfill our mission and protect your privacy
Sustained funding is key to quickly releasing new features requested by you and other community members
Being self-funded and independent, we can personally promise you
that we will never sell your data and that we will always be transparent
about our software and services
Please also leave a star on GitHub if you like this project. It provides additional motivation to keep going.
A big thank you to all current and past sponsors,
whose generous support has been and continues to be essential to the
success of the project!
Our Project Roadmap
shows what tasks are in progress and what features will be implemented
next. You are invited to give ideas you like a thumbs-up, so we know
what's most popular.
Be aware that we have a zero-bug policy and do our best to
help users when they need support or have other questions. This comes
at a price though, as we can't give exact release dates for new
features. Our team receives many more requests than can be implemented,
so we want to emphasize that we are in no way obligated to implement the
features, enhancements, or other changes you request. We do, however,
appreciate your feedback and carefully consider all requests.
We kindly ask you not to report bugs via GitHub Issues unless you are certain to have found a fully reproducible and previously unreported issue that must be fixed directly in the app. Thank you for your careful consideration!
When browsing issues, please note that our team and all issue subscribers receive an email notification from GitHub whenever a new comment is added, so these should only be used for sharing important information and not for discussions, questions, or expressing personal opinions
Contact us or a community member if you need help, it could be a local configuration problem, or a misunderstanding in how the software works
This gives us the opportunity to improve our documentation
and provide best-in-class support instead of dealing with
unclear/duplicate bug reports or triggering a flood of notifications by
replying to comments
Connect with the Community
Follow us on Mastodon, Bluesky, or join the Community Chat to get regular updates, connect with other users, and discuss your ideas. Our Code of Conduct explains the "dos and don’ts" when interacting with other community members.
As a contributor, you are also welcome to contact us directly
if you have something on your mind that you don't want to discuss
publicly. Please note, however, that due to the high volume of emails we
receive, our team may be unable to get back to you immediately. We do
our best to respond within five business days or less.
Every Contribution Makes a Difference
We welcome contributions of any kind, including blog posts, tutorials, translations, testing, writing documentation, and pull requests. Our Developer Guide contains all the information necessary for you to get started.
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
Awesome Codex Skills
A curated list of practical Codex skills for automating workflows across the Codex CLI and API.
Want skills that do more than generate text? Codex can send emails, create issues, post to Slack, and take actions across 1000+ apps. See how →
Quickstart: Add Skills to Codex
Install with the Skill Installer (recommended)
git clone https://github.com/ComposioHQ/awesome-codex-skills.git
cd awesome-codex-skills
# Install one or more skills into $CODEX_HOME/skills (defaults to ~/.codex/skills)
python skill-installer/scripts/install-skill-from-github.py --repo ComposioHQ/awesome-codex-skills --path meeting-notes-and-actions
The installer fetches the skill and places it in $CODEX_HOME/skills/<skill-name>. Restart Codex to pick up new skills.
Manual install
Copy the desired skill folder (e.g., ./spreadsheet-formula-helper) into $CODEX_HOME/skills/ (defaults to ~/.codex/skills/).
Restart Codex so it loads the new metadata.
In your next session, describe the task or mention the skill name; Codex will trigger matching skills based on their description frontmatter.
Contents
Bernstein - Multi-agent orchestrator with Codex CLI adapter. Runs parallel Codex agents in isolated git worktrees with quality gates.
Codex skills are modular instruction bundles that tell
Codex how to execute a task the way you want it done. Each skill lives
in its own folder with a SKILL.md that includes metadata
(name + description) and step-by-step guidance. Codex reads the metadata
to decide when to trigger a skill and loads the body only after it
fires, keeping context lean.
Skills
Development & Code Tools
brooks-lint -
AI code reviews grounded in six classic engineering books — decay risk
diagnostics with book citations, severity labels, and four analysis
modes (PR review, architecture audit, tech debt, test quality). Install:
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py --repo hyhmrright/brooks-lint --path skills/brooks-lint --name brooks-lint
bringyour-migration-auditor
- Audit Claude Code to Codex harness migrations for AGENTS.md/CLAUDE.md
scope, hooks, MCP config, skills, secrets, and validation notes.
Install: python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py --repo unitedideas/bringyour-mcp --path skills/bringyour-migration-auditor --name bringyour-migration-auditor
codebase-migrate/ - Run large codebase migrations and multi-file refactors in reviewable batches with CI verification.
codebase-recon
- Analyze git history to understand a codebase before reading any code —
surfaces hotspots, bug magnets, bus factor, momentum, and high-risk
files (hotspot ∩ bug-magnet) via auto-scaled analysis. Install: python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py --repo yujiachen-y/codebase-recon-skill --path skills/codebase-recon --name codebase-recon
create-plan/ - Quickly draft concise execution plans for coding tasks.
deploy-pipeline/ - End-to-end Stripe → Supabase → Vercel release pipelines with verify and rollback.
Vibe-Skills
- Governed Codex skill harness for staged, test-driven work: routes
340+ skills through requirement freeze, plan approval, execution,
verification evidence, and cross-session memory.
polywave
- Parallel agent coordination with structural merge safety. Scout
decomposes, Wave agents implement in isolated worktrees with disjoint
file ownership. Same protocol on Claude Code and Codex.
Productivity & Collaboration
connect/ - Connect Codex to 1000+ apps via the Composio CLI for real actions (Slack, GitHub, Notion, etc.).
connect-apps/ - Wire up Composio CLI connections for Claude and kick off app workflows from the shell.
issue-triage/ - Triage Linear or Jira backlogs and run bug sweeps from the terminal.
linear/ - Manage issues, projects, and team workflows in Linear.
support-ticket-triage/ - Triage customer support tickets with categories, priority, next actions, and draft replies.
file-organizer/ - Organize, rename, and tidy files to keep workspaces clean.
paperjsx/
- Generate PPTX presentations, DOCX documents, XLSX spreadsheets, and
PDF invoices/reports/charts from structured JSON. Runs locally via @paperjsx/mcp-server — no API key, no network calls.
skill-share/ - Share skills and reusable instructions across teammates.
Communication & Writing
codex-sms-verification
- External repo: real-SIM SMS verification for AI agents via VirtualSMS
MCP. 145+ countries, 2000+ services, both hosted (mcp.virtualsms.io)
and local stdio transports.
email-draft-polish/ - Draft, rewrite, or condense emails for the right tone and audience.
diasporic-intelligence
- External repo: source-credit skill for consent-governed lineage AI
with attribution, provenance, revocation, and non-impersonation
boundaries.
novel-writing - External repo: public Codex skill for fiction planning, chapter drafting, scene continuation, and revision.
unslop
- External repo: CLI and MCP server that removes AI writing patterns
from text: tricolons, em-dash overuse, hedging stacks, and sycophancy
openers. Works with Codex, Claude Code, Gemini CLI, and Cursor. Five
intensity levels and a lint-only audit mode.
skill-installer/ - Helper scripts to install skills from curated lists or GitHub paths.
skill-creator/ - Guidance for building effective Codex skills with progressive disclosure.
Using Skills in Codex
Skills live in $CODEX_HOME/skills (default ~/.codex/skills). Each subfolder needs a SKILL.md with name and description frontmatter.
After installing or updating a skill, restart Codex so it reloads metadata.
In a session, describe the task naturally; Codex auto-triggers
skills whose descriptions match the request. You can also mention a
skill by name if you want it considered.
To verify installation, list installed skills (ls ~/.codex/skills) and inspect metadata (head ~/.codex/skills/<skill>/SKILL.md).
Creating Skills
Skill layout:
skill-name/
├── SKILL.md # Required: instructions + YAML frontmatter
├── scripts/ # Optional: helper scripts for deterministic steps
├── references/ # Optional: long-form docs loaded only when needed
└── assets/ # Optional: templates or files used in outputs
Basic SKILL.md template:
---name: my-skill-namedescription: What the skill does and when Codex should use it.---# My Skill Name
Clear instructions and steps for Codex to execute the task.
Best practices:
Keep the description exhaustive about when to trigger; keep the body focused on execution steps.
Use progressive disclosure: put detailed references in references/ and call them out from SKILL.md only when needed.
Include scripts for repeatable or deterministic operations; mention when Codex should run them.
Avoid extra docs (README, changelog) inside the skill folder to keep context lean.
Join the Community
Join our Discord - Chat with other developers building Codex skills.
"FEATURE : SURFING WEB WITHOUT ANNOYING ADS * KILL ANNOYING ADS AT FACEBOOK * FACEBOOK AUTO PHOTO ZOOM * NETWORK TWEAKING * IDM INTEGRATION MODULE * 4SHARED DIRECT DOWNLOAD WITHOUT LOGIN * ALLOWS YOU TO LOGGED INTO MULTIPLE ACCOUNT * REMOVE UNWANTED TWEET OR HASHTAG ON TWITTER * AND MUCH MORE..."
Source for BiglyBT, a feature filled, open source,
ad-free, bittorrent client. BiglyBT is forked from the original project
and is being maintained by two of the original developers as well as
members of the community. With over 20 years of development, there's a
good chance we have the features you are looking for.
Getting the basics to compile from source is pretty straightforward:
Clone the repo into your favorite IDE
Mark core/src and uis/src as project roots (source modules)
To the uis module, add core/lib/* and one of the swt.jars at /uis/lib/: swt-win64.jar on Windows swt-cocoa-64.jar on OSX swt-linux-64.jar on Linux (GTK)
To the core module, add core/lib/*
Make uis module depend on core. Core should not depend on uis
IntelliJ IDEA will do all these steps for you with its wizard.
External Annotations
If you wish IntelliJ IDEA to show MessageBundle strings
instead of keys, as well as reduce the number of NPE warnings, you can
attach the external annotations either by:
Our binaries and installers up to and including v3.4 are
signed with a digital signature of "Bigly Software". Releases after v3.4
will use an individual signing certificate and will bear the name
"Arron Mogge (Open Source Developer)" denoting the identity of our team
member responsible for signing.
