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 ATTCKDigital/smith --skill smith-reportgit clone --depth 1 https://github.com/ATTCKDigital/smithWrote 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/attckdigital/smith/smith-report)<a href="https://agentmods.dev/skills/attckdigital/smith/smith-report"><img src="https://agentmods.dev/badge/skills/attckdigital/smith/smith-report/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/attckdigital/smith/smith-report"><img src="https://agentmods.dev/badge/skills/attckdigital/smith/smith-report.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.00028 | $0.01886 |
| Opus 5.5 | $0.00011 | $0.00754 |
| Sonnet 5.5 | $0.00006 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
smith-report 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smith Client Report Generator
Generate polished, client-facing project reports by synthesizing vault session logs, git history, spec artifacts, and audit results into a professional narrative.
Arguments: $ARGUMENTS
Vault Logging
Throughout this action, log significant events to the vault session log. Read the session log path from .smith/vault/.current-session. If the file is missing or the vault is not initialized, skip all logging silently.
Timestamps are UTC. HH:MM:SS comes from date -u +%H:%M:%S — never a local clock, never a time from memory. The append already runs through a shell, so read the clock in that same command (TS=$(date -u +%H:%M:%S)) and spend no extra tool call. Substitute the resulting value: an unexpanded $(...) reaching the log is a known regression and will not parse. Every hook-written stamp in this log is date -u, so a local-clock entry lands hours away from its neighbours and skews the workflow window hooks/workflow_summary_lib.py derives from them.
Append entries using this format:
### [HH:MM:SS] /smith-report <event>
**User Request:**
> <verbatim user message that triggered this action>
**Synthesized Input:** <brief summary>
**Outcome:** <what happened>
**Artifacts:** <files created>
**Systems affected:** <system IDs>
Log at these points:
- On invocation — date range, report type, project
- After generation — path to output file, report summary
Step 1: Gather Parameters
If $ARGUMENTS contains flags, parse them. Otherwise prompt for each missing parameter in a single message:
Date range (required):
week— past 7 daysmonth— past 30 daysYYYY-MM-DD:YYYY-MM-DD— custom range
Report type (required):
progress— what was built, what's in progress, what's nextdecisions— key decisions made and their reasoningspecs— which specs were created, modified, or completedfull— combines all of the above
Project (optional, defaults to current working directory):
- Read from
~/.smith/projects.jsonif multiple projects registered
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 Changed · +2 lines 9ba9eba86f55
- 1mo ago First seen · 232 lines · 28 tokens per session scan A 618bd171ad2f
smith-report is a skill published in the GitHub repository ATTCKDigital/smith (54 stars, last pushed 7d ago), licensed MIT. It adds 28 tokens to every session and 1,886 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
notion
Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.
notion
Search, read, create, and update Notion pages via the Notion MCP.
recipe-create-doc-from-template
Copy a Google Docs template, fill in content, and share with collaborators.
bo-runbook
A reusable step-by-step operating manual for a repeated task or handoff. It covers prerequisites, normal steps, checks that show success, failure handling, and escalation when those details are provided.
reversa-sync
Convergência pós-coding do Reversa: destila a feature entregue num adendo em reversasdd/addenda/, mantendo a extração representativa entre re-extrações, sem tocar nos artefatos originais. Passo opcional do ciclo forward após /reversa-coding.
prismer-notion
Notion API + ntn CLI: pages, databases, markdown, Workers.