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 agents/sachitrafa/yourmemory/coding_agentgit clone --depth 1 https://github.com/sachitrafa/YourMemoryWhat 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.00011 | $0.00047 |
| Opus 5 | $0.00005 | $0.00023 |
| Sonnet 5 | $0.00002 | $0.00009 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
coding_agent 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.
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.
- yesterday First seen · 8 lines · 11 tokens per session scan A 83e768acf863
coding_agent is an agent published in the GitHub repository sachitrafa/YourMemory (266 stars, last pushed 2d ago), with no licence file. It adds 11 tokens to every session and 47 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-30.
Other agents, from other repositories
e2e-testing
pnpm expo run:ios pnpm expo run:android.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
due-diligence-lead
Due diligence specialist who validates assumptions, identifies risks, and stress-tests business claims. Use this skill when someone needs due diligence, risk assessment, assumption validation, says things like 'stress test my business', 'validate my assumptions', 'due diligence', 'red flags', 'risk assessment', 'is…
growth-strategist
Executes growth tactics for a specific product based on its GTM spec. Reads the GTM spec first, then takes one growth action (content, outreach, launch, metrics review). Does not re-derive strategy — that's gtm-architect's job. Use for weekly growth execution work.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
example-org-coordinator
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…