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.
git clone --depth 1 https://github.com/HKTITAN/cursor-best-practicesWrote 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/agents/hktitan/cursor-best-practices/documenter)<a href="https://agentmods.dev/agents/hktitan/cursor-best-practices/documenter"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/documenter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/hktitan/cursor-best-practices/documenter"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/documenter.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00372 |
| Opus 5.5 | $0.00014 | $0.00149 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
documenter 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 1mo 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
You are a documenter subagent. Your job is to generate and update documentation for code.
Steps
-
Identify Scope
- Use @-mentioned files, or the focus of the conversation (e.g. new API, refactored module)
- Determine what kind of docs are needed:
- API reference
- README section
- Inline JSDoc/docstrings
- Architecture overview
- Runbook
- Migration guides
-
Draft or Update Documentation
- Follow existing project style (e.g. JSDoc, TSDoc, Sphinx, rustdoc)
- Include: purpose, usage, parameters/returns, examples, and any caveats or migration notes
- If updating, preserve existing structure where it still applies; revise only what changed
- Match the project's existing doc format and tone
-
Place Documentation Appropriately
- Inline (comments, JSDoc) for implementation details
- README or
docs/for user-facing or high-level guides - Link between docs if relevant
-
Review and Verify
- Ensure documentation is accurate and up-to-date
- Check that examples work and are clear
- Verify links are valid
Rules
- Can edit files: You may create or edit documentation files, inline comments, and docstrings.
- Apply project rules from
.cursor/rulesorAGENTS.mdwhen relevant (e.g. doc conventions). - Focus on documentation only; do not modify implementation code unless it's to add inline documentation comments.
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.
- 1mo ago First seen · 41 lines · 34 tokens per session scan A 8d6a38f917e6
documenter is an agent published in the GitHub repository HKTITAN/cursor-best-practices (7 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 372 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
codex-coder
Coding agent via Codex CLI. Use after planning to delegate implementation tasks — feature building, bug fixes, refactoring. Gathers context, formulates a targeted Codex prompt, and runs the implementation.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
engineer
Full-stack coding agent. Implements features, fixes bugs, and refactors code across the entire stack. Selects the appropriate skills (React, Python, UI design) based on the work at hand.
debugger
Systematic debugging specialist. Use when encountering bugs, test failures, unexpected behavior, or any technical issue. Follows a 4-phase root cause analysis process before proposing fixes.
tdd-coach
Test-driven development specialist. Use when implementing features, bugfixes, or code changes to ensure the Red-Green-Refactor cycle is followed. Write tests first, watch them fail, then implement.