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 Kastalien-Research/thoughtbox --skill workflows-reviewgit clone --depth 1 https://github.com/Kastalien-Research/thoughtboxWrote 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/kastalien-research/thoughtbox/workflows-review)<a href="https://agentmods.dev/skills/kastalien-research/thoughtbox/workflows-review"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/workflows-review/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/kastalien-research/thoughtbox/workflows-review"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/workflows-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.01306 |
| Opus 5.5 | $0.00008 | $0.00522 |
| Sonnet 5.5 | $0.00004 | $0.00261 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
workflows-review 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review the implementation: $ARGUMENTS
Purpose
You are executing Stage 5 (Review) of the development workflow. Implementation is complete and sub-agent summaries exist on disk. Your job is to dispatch review agents that verify claims, check for regressions, and assess quality. You do NOT fix issues — that's Stage 6's job.
Pre-Conditions
Before starting, verify:
.workflow/state.jsonexists andcurrentStageis"review"- Implementation summaries exist (check
stages.implementation.artifacts.summariesin state) - Read each summary to build the claims list
If pre-conditions are not met, report what's missing and halt.
Process
Step 1: Collect Claims
Read all sub-agent summaries from .workflow/summaries/*.md. Extract:
- Every claim from each summary's
### Claimssection - Every test command from
### Testssection - Every spec claim alignment statement from
### Spec/Evidence Alignment - Every risk from
### Riskssection
Step 2: Dispatch Review Agents
Dispatch specialized review agents in parallel. Each gets the full claims list and the relevant source files.
Required reviews (always run these):
-
Claim Verification — Use a
general-purposeagent to:- Run every test command listed in summaries
- Verify each claim by reading the implementation
- Flag claims that are unsupported or contradicted
-
Type Safety — Use the
compound-engineering:review:kieran-typescript-revieweragent (or dispatch via Agent tool with instructions to check types):- Run
npm run buildortsc --noEmit - Check for type errors, unsafe casts, any-typed escape hatches
- Run
-
Pattern Consistency — Use
compound-engineering:review:pattern-recognition-specialistagent:- Check that new code follows existing codebase patterns
- Flag naming inconsistencies, structural deviations
Conditional reviews (run when relevant):
- Security — If changes touch auth, input handling, or external APIs:
- Use
compound-engineering:review:security-sentinelagent
- Use
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 · 158 lines · 21 tokens per session scan A 901f1b5111f2
workflows-review is a skill published in the GitHub repository Kastalien-Research/thoughtbox (65 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 1,306 once invoked, about $0.0001 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-30.
Other skills, from other repositories
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
code-review
Review ServiceNow server-side scripts for ES5 violations, ACL/injection/XSS issues, N+1 queries, missing setLimit/error handling, hard-coded sysids, and business-rule recursion risks.
remarc
Manage Remarc session comments and contextual feedback. Use when the user mentions Remarc sessions, comments, handoff, triage, review, addressing, resolving, status updates, or summaries.
gh-address-comments
This skill should be used when addressing GitHub pull request review comments systematically with mandatory resolution tracking. Use when user says "address PR comments", "fix review feedback", "handle PR review", "resolve PR threads", or needs to ensure all review comments are addressed before merging. Fetches…
stage-refactor-checklist
Comprehensive checklist for refactoring a schemacompiler stage folder. Use EVERY TIME you refactor a compiler stage (resolve, unify, codegen, etc.). Read this before writing any code.