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 statusgit 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/status)<a href="https://agentmods.dev/skills/kastalien-research/thoughtbox/status"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/status/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/status"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/status.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.00030 | $0.00230 |
| Opus 5.5 | $0.00012 | $0.00092 |
| Sonnet 5.5 | $0.00006 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
status 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.
What it actually says
Generate a comprehensive status report by running these checks:
!git log --oneline -10 2>/dev/null || echo "No recent commits"
!git branch -a --sort=-committerdate | head -10 2>/dev/null || echo "No branches"
!gh issue list --limit 10 2>/dev/null || echo "No GitHub issues available"
!gh pr list --limit 10 2>/dev/null || echo "No open PRs"
Summarize findings in this format:
Status Report
Recent Activity
[List recent commits and active branches]
Open PRs
[List open pull requests and their status]
Open Issues
[List open GitHub issues]
Project Health
[Summary of activity level, branch hygiene, PR backlog]
Recommendations
[Suggested next actions based on current state]
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 · 37 lines · 30 tokens per session scan A d34178bfc2f9
status is a skill published in the GitHub repository Kastalien-Research/thoughtbox (65 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 230 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
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
git-workflow
Trunk-based git workflow with worktrees, switch/restore over checkout, Conventional Commits, force-with-lease. Use whenever the user asks me to commit, push, branch, or rebase.
project-briefing
Generate an executive briefing of the last 24 hours of commits for the current project or a specified directory. Use when the user asks for a project update, daily briefing, commit summary, "what changed today," or wants to stay up-to-date with recent work.
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.