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 quatico-solutions/agent-skills --skill show-your-workgit clone --depth 1 https://github.com/quatico-solutions/agent-skillsWrote 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/quatico-solutions/agent-skills/show-your-work)<a href="https://agentmods.dev/skills/quatico-solutions/agent-skills/show-your-work"><img src="https://agentmods.dev/badge/skills/quatico-solutions/agent-skills/show-your-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/quatico-solutions/agent-skills/show-your-work"><img src="https://agentmods.dev/badge/skills/quatico-solutions/agent-skills/show-your-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.00093 | $0.01110 |
| Opus 5 | $0.00046 | $0.00555 |
| Sonnet 5 | $0.00019 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
show-your-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 11d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show Your Work
Build a reproducible demo document that proves completed work — tests passing, UI correct, changes verified.
Tools: showboat (docs) + rodney or project-native tools (screenshots). Setup: ./install-dependencies.sh. Commands: showboat --help, rodney --help.
When to Use
Reactive (work complete): Review what changed (git diff, task context), capture evidence retrospectively.
Proactive (still implementing): Add a "Demo" subsection to the plan, build the document as each step completes.
When NOT to use:
- Trivial changes (config tweaks, dependency bumps)
- User explicitly declined a demo
- Pure internal refactoring with no user-facing behavior
Workflow Checklist
- [ ] showboat --help (verify tool available)
- [ ] showboat init docs/demos/YYYY-MM-DD-<slug>.md "Title"
- [ ] showboat note — what changed and why
- [ ] showboat exec — test runs, build output, key commands
- [ ] Screenshots if UI changed (see tool selection below)
- [ ] showboat verify — re-run if outputs changed
- [ ] Commit demo + images (D intention, droppable on merge)
- [ ] Offer to attach key sections to PR description
Screenshots
Prefer project-native tools over rodney:
| If the project uses... | Use for screenshots |
|---|---|
| Playwright (BDD tests, MCP debugging) | Playwright screenshot API or test artifacts |
| Cypress | Test runner output or cy.screenshot() |
| Other test runner with screenshots | Reuse existing test artifacts |
| None of the above | uvx rodney (see rodney --help) |
Embed with showboat image <doc> <image-path>.
Output Location
| Situation | Location | Committed? |
|---|---|---|
| Default | docs/demos/ |
Yes |
| User specifies non-git destination | tmp/ |
No |
| Project rules specify another location | Follow project rules | Depends |
Naming: YYYY-MM-DD-<slug>.md, images as *-<description>.png.
Sharing the Demo
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.
- 11d ago First seen · 100 lines · 93 tokens per session scan A 89353dcd4c33
show-your-work is a skill published in the GitHub repository quatico-solutions/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 93 tokens to every session and 1,110 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.