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/mmletgo/cc-partner/cargo-target-cachegit clone --depth 1 https://github.com/mmletgo/cc-partnerWhat 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.00256 | $0.00256 |
| Opus 5 | $0.00128 | $0.00128 |
| Sonnet 5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
cargo-target-cache 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 15 lines · 256 tokens per session scan A 95c899247330
cargo-target-cache is a cursor rule published in the GitHub repository mmletgo/cc-partner (5 stars, last pushed 2d ago), with no licence file. It adds 256 tokens to every session, about $0.0013 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 cursor rules, from other repositories
050-plan
When the user types /plan or asks to create a project plan, feature PRD, or retrospective.
project
4DA project rules and conventions.
graphql
GraphQL: schema design, resolvers, performance.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
context-routing
System, platform, and developer instructions take precedence; then repository-specific rules; then this framework. Before work, read .ai/bootstrap/boot.md and .ai/rules/00-master-rules.md. Load focused rules and skills only when triggered.
fcop-protocol
FCoP Protocol commentary (behavior governance protocol layer · v3 — lifecycle/-based collaboration) — the protocol commentary on the rules defined in fcop-rules.mdc. Covers file naming, YAML frontmatter, v3 lifecycle/ directory layout, lifecycle state machine, patrol triggers, and other practical conventions.…