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 hatawong/claude-recap --skill ignore-topicgit clone --depth 1 https://github.com/hatawong/claude-recapWrote 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/hatawong/claude-recap/ignore-topic)<a href="https://agentmods.dev/skills/hatawong/claude-recap/ignore-topic"><img src="https://agentmods.dev/badge/skills/hatawong/claude-recap/ignore-topic/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hatawong/claude-recap/ignore-topic"><img src="https://agentmods.dev/badge/skills/hatawong/claude-recap/ignore-topic.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.00536 |
| Opus 5 | $0.00025 | $0.00268 |
| Sonnet 5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
ignore-topic 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ignore-topic — 100% identical, 0 lines differ
What it actually says
ignore-topic
Manage .ignore rules — glob patterns that prevent matching topic slugs from being archived. Topics still get tagged but archival is skipped (no LLM summary call, no file written).
Step 1: Determine operation
Parse the user's message for operation (add/remove/list) and patterns. If clear, skip to Step 2.
Otherwise, ask using AskUserQuestion:
What would you like to do?
- Add: Add ignore patterns (topics matching these will not be archived)
- Remove: Remove an existing ignore pattern
- List: Show all current ignore rules
Step 2: Execute
add:
- If no patterns provided, ask for patterns (space-separated, glob supported:
*,?,[...]). - Ask scope via AskUserQuestion:
Which scope? - Global: applies to all projects (~/.memory/.ignore) - Project: applies only to this project - Run:
bash "<plugin_scripts_path>/ignore-topic.sh" add "<scope>" <pattern1> [pattern2 ...]<scope>:globalor the project dir path from SessionStart context.
remove:
- If no pattern provided, ask which pattern to remove.
- Ask scope (global or project).
- Run:
bash "<plugin_scripts_path>/ignore-topic.sh" remove "<scope>" "<pattern>"
list:
bash "<plugin_scripts_path>/ignore-topic.sh" list "<project_dir>"
Path resolution
<plugin_scripts_path>: from SessionStart injectionPlugin scripts path: ...<project_dir>: from SessionStart injectionYour persistent memory is stored at <project_dir>
Examples
| User says | Operation | Scope question? |
|---|---|---|
/ignore-topic add git-* lint-fix |
add git-* and lint-fix |
Yes |
/ignore-topic |
Ask all | Yes |
/ignore-topic list |
list | No |
| "don't archive run-tests topics" | add run-tests |
Yes |
/ignore-topic remove git-* |
remove git-* |
Yes |
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.
- 10d ago First seen · 69 lines · 50 tokens per session scan A 12d8d3aabbd6
ignore-topic is a skill published in the GitHub repository hatawong/claude-recap (39 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 536 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
memory-write
Captures a durable fact to project memory through the kit's safe write path (PoisonGuard secret/injection screening + home-path sanitization + dedup + conflict detection) — preferring the cmk MCP tools (mkremember / mkforget / mktrust) when connected, falling back to the cmk CLI. Use when the user says "remember…
bootstrap
Scaffolds the core-memory-kit directory structure (context/, scripts/, cron/jobs/) into the current project. Idempotent — never overwrites existing files. Run once per project after installing the plugin. Use when the user says "bootstrap the memory system", "set up memory here", or "scaffold the memory kit".
troubleshooting
Diagnoses and repairs core-memory-kit itself when the memory system is broken — the per-failure-code repair book. Fire whenever a "⚠ [core-memory-kit]" whisper appears on the prompt (it names the failure and points here), or when the user reports a kit symptom however they phrase it: memory is not being saved, nothing…
memory-search
Searches the project's recorded memory (core-memory-kit) — decisions, conventions, architecture, the reasoning behind choices, and where things live — and returns a curated, cited summary. Fire whenever the answer might be something the project already established in past work, HOWEVER the question is phrased — any…
mem9
Persistent cloud memory for OpenClaw agents. Use when users say: "install mem9" "setup memory" "add memory plugin" "openclaw memory" "mem9 onboarding" "memory not working" "import memories" "upload sessions".
mem9
Persistent cloud memory for OpenClaw agents. Use when users say: "install mem9" "setup memory" "add memory plugin" "openclaw memory" "mem9 onboarding" "memory not working" "import memories" "upload sessions".