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 rules/jstxn/agentdir/agentdirgit clone --depth 1 https://github.com/jstxn/agentdirWhat 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.00631 | $0.00631 |
| Opus 5 | $0.00316 | $0.00316 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
agentdir 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 2d 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
AgentDir for Cursor
AgentDir is agent-owned background instrumentation for this repository. The engineer installs or adopts it once; agents operate it during normal work.
- Before starting work in an unfamiliar checkout, run
agentdir root --require --quiet. Exit 0 means an initialized local or shared worktree store is ready; do not decide whether AgentDir is set up from the presence of.agentdirin this checkout. - If the probe exits 3, run
agentdir adopt --if-needed --gitignore user. If hook installation is blocked in a restricted linked worktree, rerun it with--no-hooks. - Then start non-trivial coding work yourself with
agentdir work start "<subsystem: distinctive behavior or constraint>". Keep the title concise but retrieval-specific: name the subsystem plus a distinctive behavior or constraint, preserving request terms likely to match prior work. - Read the printed context briefing, treat excerpts as previews, and prefer the printed
agentdir work context --pack <pack-id> --expand <number>command before using a source when implementation details, prior patterns, or exact evidence matter. Then close the review once: repeat--usein that command for every useful numbered source (agentdir work context --use <number> [--use <number> ...] --reason "<how they help>"), or runagentdir work context --none-relevant --reason "<why>". Use--skip --reason "<why>"only when review is impossible; no decision is needed when no sources are presented. Re-open lost output withagentdir work context --show. - Wrap evidence-bearing commands with
agentdir run -- <command>. - Evidence includes tests, lint, typecheck, builds, doctor checks, release checks, reproduced failures, and diagnostics used in final claims.
- Do not wrap routine exploration such as
rg,sed,nl,cat,ls,find, or quick read-onlygit status. - Use
agentdir evidence --briefandagentdir timelineto skim what happened. - Record each verification you will rely on with
agentdir claim <family> --passed|--failed, e.g.agentdir claim test --passed. Families: test, lint, typecheck, build, doctor, release. - Claim what the evidence shows, including failures.
agentdir audit claimscompares recorded claims against evidence, so a claim that overstates a result is reported as contradicted. - Re-recording a family replaces its earlier claim; withdraw one made in error with
agentdir claim <family> --retract. - Use
agentdir report final --format jsonoragentdir work finish --json --brieffor the agent handoff object before final claims when practical. - Do not record secrets, private keys, raw environment dumps, or credential-bearing command output.
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.
- 2d ago First seen · 26 lines · 631 tokens per session scan A 8b885e96c7f9
agentdir is a cursor rule published in the GitHub repository jstxn/agentdir (21 stars, last pushed 11d ago), licensed MIT. It adds 631 tokens to every session, about $0.0032 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.