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 agentmods add commands/jansenanalytics/claudex/projectgit clone --depth 1 https://github.com/JansenAnalytics/claudexWhat 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 | $0.00020 | $0.00475 |
| Opus 5 | $0.00010 | $0.00237 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
project 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 yesterday.
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
Switch focus to a project ($ARGUMENTS) and report its live state. No fluff.
PI="node ${PROJECT_INDEX_HOME:-$HOME/projects/project-index}/index.cjs"
-
No arg — run
$PI list(fallbackls ~/projectsif it errors). Present active projects as a bullet list: name, status, one-line last_action. Stop here; tell the user to pass a name for detail. -
<name>given — gather registry + LIVE state:$PI show <name>→ pullstatus,last_action,next_steps.- If not in index, fall back to
~/projects/<name>as the path. cdinto the project path, then in ONE shell run:git rev-parse --abbrev-ref HEAD(branch),git status --porcelain | wc -l(uncommitted count),git log -5 --oneline(recent commits). If not a git repo, say so and skip git.- If
CLAUDE.mdorDESIGN.mdexists at the path, Read it and surface a 1–2 line gist (what it is / current focus).
-
Telegram summary for the named project, bullets only:
- {name} — status, path
- Branch:
<branch>· Uncommitted: N file(s) - Recent: the 5
git loglines ascode - Last action: from registry
- 1–2 line gist from CLAUDE.md/DESIGN.md if found
- End with
**Next:** <first next_step>(or "no next_steps recorded").
Known projects for fallback paths: prop-hedge-agents (~/projects/prop-hedge-agents, branch feature/agent-restructure), prop-hedge-dashboard, brewboard (STOPPED — note it, don't start), plus any other repo under ~/projects/<name>. No markdown tables.
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.
- yesterday First seen · 28 lines · 20 tokens per session scan A 43e66b01bee4
project is a command published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 475 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.