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 skills/yamadashy/repomix/agent-carnetnpx skills add yamadashy/repomix --skill agent-carnetgit clone --depth 1 https://github.com/yamadashy/repomixWhat 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.00067 | $0.01145 |
| Opus 5 | $0.00034 | $0.00573 |
| Sonnet 5 | $0.00013 | $0.00229 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
agent-carnet 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Carnet
A tiny CLI that gives you a shared markdown notebook on disk under .carnet/<category>/<slug>.md. Notes have a 30-day default lifespan that resets every time they are read or applied; useful ones survive, stale ones drift to .trash/ automatically.
Quick reference
# Save (always pass --summary and --agent claude-code)
echo "body content" | agent-carnet save deps/iconv-issue \
--summary "iconv-esm v0.7 types broken — pin to v0.6" \
--agent claude-code \
--tags compat,esm
# Recall
agent-carnet find iconv # search summaries (does NOT bump lifespan)
agent-carnet list # category-grouped overview, sorted by last_used
agent-carnet list --sort use_count # most-applied notes first
agent-carnet show deps/iconv-issue # read full content (bumps last_used; weak use signal)
# Mark as actually applied (strong use signal — bumps last_used + use_count)
agent-carnet used deps/iconv-issue
# Maintain
agent-carnet move <from> <to>
agent-carnet rm <path> --yes
When unsure of a subcommand's full flag set, run agent-carnet <command> -h (e.g.
agent-carnet save -h, agent-carnet used -h). Each subcommand prints its own
focused help — required arguments, options, and examples — without invoking
filesystem operations.
When to save
Save proactively when you discover something worth preserving across sessions:
- Research findings that took effort to derive
- Non-obvious patterns / gotchas in the codebase
- Solutions to tricky problems
- Architectural decisions and the reasoning behind them
- In-progress work that may be resumed later
When to recall
Before starting related work or when context might exist:
agent-carnet find <topic>— quick scan of summariesagent-carnet list <category>— browse a folderagent-carnet show <path>— actually read (resetslast_used; only use when the content matters)
When to call used
Call agent-carnet used <path> after a carnet actually shaped your work:
- You applied the recorded fix and it solved the bug.
- You consulted the carnet before retrying a hypothesis and skipped a dead-end.
- You used the canonical name from a
vocabcarnet in new code instead of inventing your own.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 92 lines · 67 tokens per session scan A 08285b0a349e
agent-carnet is a skill published in the GitHub repository yamadashy/repomix (28,125 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 1,145 once invoked, about $0.0003 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 skills, from other repositories
dangerous-animals-of-pm-generator
Generate creature acronyms that name PM dysfunctions, blockers, or winning strategies. Use when you want to give your team shared vocabulary for the animals hiding in your product work.
dcf-model
Build discounted cash flow valuation workbooks in Excel.
baoyu-article-illustrator
Article illustrations: type × style × palette consistency.
openhands
Delegate coding to OpenHands CLI (model-agnostic, LiteLLM).
agentmail
Use when an agent needs AgentMail CLI email inboxes.
keybindings-help
Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify /.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".