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/jackalope-dev/moxie-docs-mcp/moxie-docsgit clone --depth 1 https://github.com/Jackalope-Dev/Moxie-Docs-MCPWrote 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/rules/jackalope-dev/moxie-docs-mcp/moxie-docs)<a href="https://agentmods.dev/rules/jackalope-dev/moxie-docs-mcp/moxie-docs"><img src="https://agentmods.dev/badge/rules/jackalope-dev/moxie-docs-mcp/moxie-docs.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 | $0.00000 | $0.00249 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
moxie-docs 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
Moxie Docs — Cursor Agent Rule
This repository uses Moxie Docs for living codebase documentation and MCP context.
When building features, refactoring code, or fixing bugs in this codebase:
Pre-Edit Workflow
- Fetch Live Context: Before writing code, call
moxie.get_ai_contextto retrieve current setup status, architecture conventions, verified build/test commands, and open documentation gaps. - Analyze Doc Impact: Call
moxie.get_doc_impactwith the list of file paths you plan to modify or delete. It returns matching conventions, doc gaps, and existing docs to update in the same PR.
Implementation Guidelines
- Follow Discovered Conventions: Adhere strictly to the codebase conventions and verified test commands returned by Moxie Docs.
- Update Docs in the Same PR: Use
moxie.propose_doc_updateto generate target file paths and updated markdown content. Write these files into your branch so documentation updates ship with the code change.
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 · 19 lines · 0 tokens per session scan A 72a7e4277f98
moxie-docs is a cursor rule published in the GitHub repository Jackalope-Dev/Moxie-Docs-MCP (2 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 249 tokens. 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 cursor rules, from other repositories
200-quality-verification-procedures
description: WHEN verifying design quality APPLY systematic procedures for validation globs: ["/.md", "/.mdc"] alwaysApply: true.
160-workflow-orchestration
WHEN executing tasks MANAGE workflow processes for consistent memory operations.
040-enhanced-complexity-framework
description: WHEN assessing task complexity ENSURE appropriate process rigor is applied globs: ["/.md", "/.mdc"] alwaysApply: true.
050-reference-verification-system
description: WHEN referencing memory files ENSURE references are verified for accuracy and relevance globs: ["/.md", "/.mdc"] alwaysApply: true.
070-section-checkpoint-system
description: WHEN tracking a multi-step task ENSURE progress tracking and verification at section boundaries globs: ["/.md", "/.mdc"] alwaysApply: true.
080-creative-phase-metrics
description: WHEN entering a creative phase ENSURE comprehensive exploration and validation globs: ["/.md", "/.mdc"] alwaysApply: true.