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 skills add tta-lab/ttal-cli --skill update-claude-mdgit clone --depth 1 https://github.com/tta-lab/ttal-cliWrote 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/skills/tta-lab/ttal-cli/update-claude-md)<a href="https://agentmods.dev/skills/tta-lab/ttal-cli/update-claude-md"><img src="https://agentmods.dev/badge/skills/tta-lab/ttal-cli/update-claude-md.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.1 | $0.00019 | $0.00425 |
| Opus 5 | $0.00010 | $0.00212 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
update-claude-md 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 7d 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
Update CLAUDE.md
Overview
After a meaningful conversation — decisions made, patterns discovered, preferences stated — the user may ask you to capture what was discussed into the project's CLAUDE.md. This ensures future sessions benefit from today's context.
Which CLAUDE.md?
Find the CLAUDE.md you own in the current repo:
- In
~/clawd/— update your agent file (e.g.yuki/CLAUDE.md,kestrel/CLAUDE.md) - In any other repo — update the project root
CLAUDE.md
If unsure, ask which file to update.
How to Update
- Review the conversation — identify decisions, preferences, patterns, or conventions that were established
- Read the current CLAUDE.md — understand what's already documented
- Add only what's new — don't duplicate existing content
- Place it in the right section — match the file's existing structure. Create a new section only if nothing fits.
- Be concise — write it as an instruction, not a narrative. Future agents need to act on it, not read a story.
What to Capture
- Workflow decisions ("always use X instead of Y")
- Tool preferences ("use og pr, not gh")
- Conventions discovered ("tests go in tests/ not test/")
- Architecture decisions ("we chose X because Y")
- Gotchas and warnings ("don't run Z, it breaks W")
What NOT to Capture
- Session-specific details (current task, in-progress work)
- Anything already in CLAUDE.md (check first!)
- Speculative conclusions from one conversation
- Temporary workarounds (unless they'll persist)
After Updating
- Show the user what you added/changed
- Commit if asked (follow the repo's commit conventions)
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.
- 7d ago First seen · 50 lines · 19 tokens per session scan A 0399847c2756
update-claude-md is a skill published in the GitHub repository tta-lab/ttal-cli (23 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 425 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 skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.