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-workgit 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-work)<a href="https://agentmods.dev/skills/kastalien-research/thoughtbox/workflows-work"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/workflows-work/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-work"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/workflows-work.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.00026 | $0.00985 |
| Opus 5.5 | $0.00010 | $0.00394 |
| Sonnet 5.5 | $0.00005 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
workflows-work 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute the implementation plan: $ARGUMENTS
Purpose
You are executing Stage 4 (Implementation) of the development workflow. A plan exists from Stage 3 with decomposed tasks. Your job is to dispatch sub-agents for each task, collect their structured summaries, and persist everything to disk.
Pre-Conditions
Before starting, verify:
.workflow/state.jsonexists andcurrentStageis"implementation"- Plan file exists (check
stages.planning.artifacts.planin state, usually.workflow/plan.md)
If pre-conditions are not met, report what's missing and halt.
Process
Step 1: Read the Plan
Read .workflow/plan.md and the spec/ADR it references. Build the task execution order from the dependency graph.
Step 2: Dispatch Sub-Agents
For each task in dependency order:
-
Dispatch a sub-agent (use the Agent tool with
subagent_type: "general-purpose") with:- The task definition from the plan (files, acceptance criteria, notes)
- The relevant spec sections
- The ADR hypotheses this task should support/test
- Instructions to return the structured summary format (see below)
-
Parallelize independent tasks: If tasks have no dependency between them, dispatch their sub-agents concurrently using parallel Agent tool calls.
-
Persist the summary immediately upon receipt:
.workflow/summaries/<branch-slug>-<task-id>.md -
Verify acceptance criteria: Check each criterion from the plan against the sub-agent's summary. If any fail, note them for review.
Sub-Agent Summary Format
Each sub-agent MUST return this format:
## Sub-Agent Work Summary
### Task
- Branch: <current branch>
- Spec: <spec path>
### Changes
- Files modified: [list]
- Files created: [list]
- Lines: +N / -N
### Claims
1. "[specific testable claim]"
- Verifiable by: [test or command]
### Spec/Evidence Alignment
- H1 "<text>": SUPPORTS / REFUTES / NO EVIDENCE -- [evidence]
### Tests
- Tests written: N
- Tests passing: N/N
- Commands: `[exact command]`
### Known Gaps
- [anything deferred or uncertain]
### Risks
- [anything that could break other parts]
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 · 142 lines · 26 tokens per session scan A 96b00a1caec9
workflows-work is a skill published in the GitHub repository Kastalien-Research/thoughtbox (65 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 985 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
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
meta-ad-manager
Front door and loop owner of a Meta (Facebook/Instagram) ad harness. Reads the brand's ads/ docs, works out which campaign the user means and which stage it is at, hands off to the stage skill that runs it (intake, strategy, creative, launch, checks, fixes, answers), and writes every stage change back to the docs. Use…
where-to-start-situation-save
Step of the where-to-start playbook: saves the founder's answers and the agreed first move with the brand, so later visits and other playbooks don't ask again. Run where-to-start instead; not for direct use.
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.