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 agentmods add skills/merlinhu1/truthmark/truthmark-documentnpx skills add merlinhu1/truthmark --skill truthmark-documentgit clone --depth 1 https://github.com/merlinhu1/truthmarkWrote 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/merlinhu1/truthmark/truthmark-document)<a href="https://agentmods.dev/skills/merlinhu1/truthmark/truthmark-document"><img src="https://agentmods.dev/badge/skills/merlinhu1/truthmark/truthmark-document.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00264 |
| Opus 5 | $0.00023 | $0.00132 |
| Sonnet 5 | $0.00009 | $0.00053 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
truthmark-document 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 4d 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
Truthmark Document
Use this skill to document existing implemented behavior when no functional-code changes are required for the task.
Quick procedure:
- Follow repository instruction files that exist in this checkout; do not assume any optional policy path exists.
- Inspect .truthmark/config.yml and configured route files (docs/truthmark/routes/areas.md; docs/truthmark/routes/areas/) only when they exist; then inspect existing canonical docs, implementation code, and tests directly.
- Document current implemented behavior; do not invent future behavior.
- May write canonical truth docs and truth routing files only; must not write functional code.
Progressive disclosure:
- support/procedure.md — read before edits or detailed auditing; contains core review questions
- support/report-template.md — read before the final report
- support/subagents-and-leases.md — read only when using subagents, leases, or accepting worker output
What ships with it
4 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.
- 4d ago First seen · 22 lines · 46 tokens per session scan A dfdecfed746f
truthmark-document is a skill published in the GitHub repository merlinhu1/truthmark (87 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 264 once invoked, about $0.0002 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-30.
Other skills, from other repositories
amby-revise
Continue an existing feature's spec (or design) — add and refine in place, with a done-guard.
amby-converge
Check the codebase against spec, plan, and tasks after implementing; append gap tasks, never edit code.
amby-specify
Turn a feature idea into a spec — user stories, EARS requirements, acceptance criteria.
amby-analyze
Cross-check spec, plan, and tasks for coverage, consistency, and dependency-graph health.
amby-design
Design the UI — wireframes, component specs, and design tokens — with a sign-off gate.
amby-implement
Execute the task list, checking off tasks and updating story status as you go.