Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add JansenAnalytics/claudex --skill project-briefgit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jansenanalytics/claudex/project-brief)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/project-brief"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/project-brief.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00048 | $0.00549 |
| Opus 5 | $0.00024 | $0.00275 |
| Sonnet 5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
project-brief scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Project Brief Skill
Use when: starting a new project, updating a project's status, or when the user asks "what's the status of X?"
Create a brief for a new project
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs new
--project
--goal "What this project does and why"
--success "criterion 1,criterion 2,criterion 3"
--constraints "constraint 1,constraint 2"
--stack "tech1,tech2"
--status "Active"
--next "first next action,second next action"
List all projects with briefs
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs list
Compact status overview
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs status
View a project's brief
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs view
Update a brief
node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --status "Complete" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --add-next "New action item" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --check "Success criterion text" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --add-history "What changed today" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --add-blocker "What's blocking" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --resolve-blocker "What's blocking" node ${PROJECT_BRIEF_HOME:-$HOME/projects/project-brief}/brief.cjs update --current-status "One-liner on current state"
Briefs live at
~/projects//BRIEF.md
When to update
- When a project's status changes
- When a blocker appears or is resolved
- When a milestone is hit
- When the user says "note that X is done"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 56 lines · 48 tokens per session scan A 59275894570b
project-brief is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 549 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gitlab-issues
Issue review and tracking on GitLab via the gitlab-api MCP server — review a project's issues, review issues across a whole group/organization, and read, create, update, or close an issue with the domain-typed tool. Use when the agent must triage a project's issues, see every issue affecting a group, open a new issue…
backlog
Manage the backlog — plan, track, navigate phases and epics. Use when planning phases, viewing roadmaps, or restructuring work.
status
Show active tracks, progress, current tasks, and blockers.
hive-workflow
Issue tracking and task management using the hive system. Use when creating, updating, or managing work items. Use when you need to track bugs, features, tasks, or epics. Do NOT use for simple one-off questions or explorations.
project-status
Inspect, validate, generate, and maintain evidence-backed project readiness. Use for weighted readiness, blockers, active and deferred effort, unknown estimates, provenance checks, one-shot live monitoring, dashboard plan/apply/check workflows, repository attachment for Codex and Claude, or local Project Status plugin…
brief
A read-only status summary assembled from work records such as tasks, priorities, decisions, requests, and commitments. It can focus on recent activity, weekly review, external reporting, or current counts.