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 jamesyang124/agent-skills --skill btwgit clone --depth 1 https://github.com/jamesyang124/agent-skillsWrote 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/jamesyang124/agent-skills/btw)<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/btw"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/btw/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/jamesyang124/agent-skills/btw"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/btw.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.00066 | $0.00925 |
| Opus 5.5 | $0.00026 | $0.00370 |
| Sonnet 5.5 | $0.00013 | $0.00185 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
btw 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
btw
Reads the current graphify knowledge graph and appends a timestamped snapshot to KNOWLEDGE_SUMMARY.md. All entries stack — the file is append-only and never deduplicated.
When to Use
After /graphify-monitor has built a knowledge graph and you want to capture the current state as a reference point. Call it whenever you want to record what the graph knows — before a big change, after an interesting discovery, or as a periodic checkpoint.
Steps
Step 1: Locate the project root
git rev-parse --show-toplevel 2>/dev/null || pwd
Store as PROJECT_ROOT.
Step 2: Verify the graph exists
ls "$PROJECT_ROOT/graphify-out/graph.json"
If missing: tell the user "graphify-out/graph.json not found. Run /graphify-monitor first to build the knowledge graph." Then stop.
Step 3: Extract graph summary
Read $PROJECT_ROOT/graphify-out/graph.json and extract:
metadata.files— number of files indexedmetadata.nodes— number of symbolsmetadata.edges— number of relationships
If metadata.nodes > 0, run a broad symbol query to get a sample:
graphify query "$PROJECT_ROOT/graphify-out/graph.json" "." 2>/dev/null | head -50
If the command fails or returns nothing, set SYMBOL_SAMPLE to (no symbols indexed for this project's file types).
Store the result as SYMBOL_SAMPLE.
Step 4: Get a UTC timestamp
date -u +"%Y-%m-%dT%H:%M:%SZ"
Store as TIMESTAMP.
Step 5: Format the entry
Construct the entry exactly as follows:
---
## Knowledge Snapshot — [TIMESTAMP]
**Files indexed:** [metadata.files]
**Symbols:** [metadata.nodes]
**Relationships:** [metadata.edges]
### Symbol Sample
[SYMBOL_SAMPLE]
Step 6: Write to KNOWLEDGE_SUMMARY.md
If $PROJECT_ROOT/KNOWLEDGE_SUMMARY.md does not exist:
Create the file with this content:
# Knowledge Summary
Chronological record of graphify knowledge graph snapshots.
Each entry captures the symbol/relationship counts and a sample of discovered symbols at that point in time.
---
## Knowledge Snapshot — [TIMESTAMP]
**Files indexed:** [metadata.files]
**Symbols:** [metadata.nodes]
**Relationships:** [metadata.edges]
### Symbol Sample
[SYMBOL_SAMPLE]
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.
- 1mo ago First seen · 127 lines · 66 tokens per session scan A ec00d3e1f760
btw is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 66 tokens to every session and 925 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
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…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.