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 backbay-labs/thrunt-god --skill thrunt-threadgit clone --depth 1 https://github.com/backbay-labs/thrunt-godWrote 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/backbay-labs/thrunt-god/thrunt-thread)<a href="https://agentmods.dev/skills/backbay-labs/thrunt-god/thrunt-thread"><img src="https://agentmods.dev/badge/skills/backbay-labs/thrunt-god/thrunt-thread/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/backbay-labs/thrunt-god/thrunt-thread"><img src="https://agentmods.dev/badge/skills/backbay-labs/thrunt-god/thrunt-thread.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.00012 | $0.00788 |
| Opus 5 | $0.00006 | $0.00394 |
| Sonnet 5 | $0.00002 | $0.00158 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
thrunt-thread 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
Parse $ARGUMENTS to determine mode:
<mode_list> If no arguments or $ARGUMENTS is empty:
List all threads:
ls .planning/threads/*.md 2>/dev/null
For each thread, read the first few lines to show title and status:
## Active Threads
| Thread | Status | Last Updated |
|--------|--------|-------------|
| fix-deploy-key-auth | OPEN | 2026-03-15 |
| pasta-tcp-timeout | RESOLVED | 2026-03-12 |
| perf-investigation | IN PROGRESS | 2026-03-17 |
If no threads exist, show:
No threads found. Create one with: /thrunt-thread <description>
</mode_list>
<mode_resume> If $ARGUMENTS matches an existing thread name (file exists):
Resume the thread — load its context into the current session:
cat ".planning/threads/${THREAD_NAME}.md"
Display the thread content and ask what the user wants to work on next.
Update the thread's status to IN PROGRESS if it was OPEN.
</mode_resume>
<mode_create> If $ARGUMENTS is a new description (no matching thread file):
Create a new thread:
-
Generate slug from description:
SLUG=$(node ".github/thrunt-god/bin/thrunt-tools.cjs" generate-slug "$ARGUMENTS") -
Create the threads directory if needed:
mkdir -p .planning/threads -
Write the thread file:
cat > ".planning/threads/${SLUG}.md" << 'EOF' # Thread: {description} ## Status: OPEN ## Goal {description} ## Context *Created from conversation on {today's date}.* ## References - *(add links, file paths, or issue numbers)* ## Next Steps - *(what the next session should do first)* EOF -
If there's relevant context in the current conversation (code snippets, error messages, investigation results), extract and add it to the Context section.
-
Commit:
node ".github/thrunt-god/bin/thrunt-tools.cjs" commit "docs: create thread — ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md" -
Report:
## 🧵 Thread Created Thread: {slug} File: .planning/threads/{slug}.md Resume anytime with: /thrunt-thread {slug}
</mode_create>
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 · 126 lines · 12 tokens per session scan A 825675404445
thrunt-thread is a skill published in the GitHub repository backbay-labs/thrunt-god (36 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 788 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-09-03.
Other skills, from other repositories
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
pod-resume
Reconstruct context for a returning developer. Reads .cocoplus/ state and generates a narrative summary of project status, last achievements, pending tasks, recent decisions, available patterns, CocoCupper insights, and recommended next action.
td-task-management
Task management for AI agents across context windows. Use when agents need to track work, log progress, hand off state, and maintain context across sessions. Includes workflows for single-issue focus, multi-issue work sessions, and structured handoffs. Essential for AI-assisted development where context windows reset…
register-project
Register an existing project in memory. Use when starting work on a new repo or when a project needs its own context file. Triggers on: 'register project', 'add project to memory', 'track this project', 'create project file'.
chainabit-operator
The Chainabit-owned operator lenser that runs weekly reviews, async standups, PR triage, and launch content kits.
specsfy-setup
Preparar, monitorar ou reconciliar o contexto persistente de um projeto Specsfy. Use ao iniciar o framework, antes e depois de mudanças na aplicação, ao verificar consistência documental, quando PROJECT.md ou os arquivos .specsfy/STACK.md, .specsfy/RULES.md e .specsfy/DATABASE.md estiverem ausentes, ou quando for…