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 bravew/trove --skill trove-show-workgit clone --depth 1 https://github.com/bravew/troveWrote 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/bravew/trove/trove-show-work)<a href="https://agentmods.dev/skills/bravew/trove/trove-show-work"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-show-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/bravew/trove/trove-show-work"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-show-work.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.00054 | $0.00448 |
| Opus 5.5 | $0.00022 | $0.00179 |
| Sonnet 5.5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
trove-show-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.
What it actually says
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
trove-show-work
Maintain one canonical decision log so a reviewer can reconstruct an unattended run without replaying it. Local by default; commit it when a reviewer needs the trail to trust the result.
The log
One TSV file, append-only, one row per decision. Columns: ts, phase, decision, why, evidence, result. TSV because GitHub renders it as a sortable table and column -s$'\t' -t file.tsv reads it in a terminal. Template: references/decision-log-template.tsv.
Use the helper so timestamps and the formula-injection guard are consistent:
scripts/log.sh decisions.tsv "<phase>" "<decision>" "<why>" "<evidence>" "<result>"
- Append-only. A wrong call doesn't get edited away — add a new row that supersedes it and say so in
result. The history is the point. - Evidence is mandatory. The
evidencecell points at the real thing (a command output, a file:line, a metric), not "looks right".
Self-audit before handoff
Read the log against what actually happened this session. Fix the log, not the story: if a row claims an outcome the transcript doesn't support, correct the row. Optionally get a second opinion from a fresh read (a sub-agent) and add an "Attention" row for anything a reviewer must look at.
Why not prose
A narrative paragraph hides the decision points. One row per decision makes a skipped verification or an unsupported claim visible at a glance.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 36 lines · 54 tokens per session scan A ceba6806ca1a
trove-show-work is a skill published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 448 once invoked, about $0.0002 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-09-11.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…