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-review-backloggit 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-review-backlog)<a href="https://agentmods.dev/skills/backbay-labs/thrunt-god/thrunt-review-backlog"><img src="https://agentmods.dev/badge/skills/backbay-labs/thrunt-god/thrunt-review-backlog/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-review-backlog"><img src="https://agentmods.dev/badge/skills/backbay-labs/thrunt-god/thrunt-review-backlog.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.00014 | $0.00499 |
| Opus 5 | $0.00007 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
thrunt-review-backlog 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 9d 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.
This is a copy
88% identical to gsd-review-backlog — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
-
List backlog items:
ls -d .planning/phases/999* 2>/dev/null || echo "No backlog items found" -
Read HUNTMAP.md and extract all 999.x phase entries:
cat .planning/HUNTMAP.mdShow each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.
-
Present the list to the user via AskUserQuestion:
- For each backlog item, show: phase number, description, accumulated artifacts
- Options per item: Promote (move to active), Keep (leave in backlog), Remove (delete)
-
For items to PROMOTE:
- Find the next sequential phase number in the active milestone
- Rename the directory from
999.x-slugto{new_num}-slug:NEW_NUM=$(node ".github/thrunt-god/bin/thrunt-tools.cjs" phase add "${DESCRIPTION}" --raw) - Move accumulated artifacts to the new phase directory
- Update HUNTMAP.md: move the entry from
## Backlogsection to the active phase list - Remove
(BACKLOG)marker - Add appropriate
**Depends on:**field
-
For items to REMOVE:
- Delete the phase directory
- Remove the entry from HUNTMAP.md
## Backlogsection
-
Commit changes:
node ".github/thrunt-god/bin/thrunt-tools.cjs" commit "docs: review backlog — promoted N, removed M" --files .planning/HUNTMAP.md -
Report summary:
## 📋 Backlog Review Complete Promoted: {list of promoted items with new phase numbers} Kept: {list of items remaining in backlog} Removed: {list of deleted items}
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.
- 9d ago First seen · 60 lines · 14 tokens per session scan A 7c49d001462d
thrunt-review-backlog is a skill published in the GitHub repository backbay-labs/thrunt-god (36 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 499 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to gsd-review-backlog, differing in 26 lines, and is treated as a copy.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
devtu-docs-quality
TOP PRIORITY skill — find and immediately fix or remove every piece of wrong, outdated, or redundant information in ToolUniverse docs. Wrong code, broken links, incorrect counts, and overlapping instructions must be fixed or removed — never left in place. Runs five phases: (D) static method scan, (C) live code…
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
taskmarket-delegate
Delegate work to the TaskMarket agent-worker market - browse open tasks, create tasks with explicit authorization, and track/submit work, so an agent can outsource instead of burning inference on unreliable or low-confidence work.