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-realizenpx skills add merlinhu1/truthmark --skill truthmark-realizegit 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-realize)<a href="https://agentmods.dev/skills/merlinhu1/truthmark/truthmark-realize"><img src="https://agentmods.dev/badge/skills/merlinhu1/truthmark/truthmark-realize.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.1 | $0.00060 | $0.00247 |
| Opus 5 | $0.00030 | $0.00123 |
| Sonnet 5 | $0.00012 | $0.00049 |
| Haiku 4.5 | $0.00006 | $0.00025 |
Grade A, and why
truthmark-realize 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 6d 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 Realize
Use this skill only when the user explicitly asks to realize truth docs into code.
Quick procedure:
- Follow repository instruction files that exist in this checkout; do not assume any optional policy path exists.
- Read the source truth docs, inspect .truthmark/config.yml and configured route files (docs/truthmark/routes/areas.md; docs/truthmark/routes/areas/) only when they exist, then inspect tests and relevant functional code directly.
- Truth docs lead; code follows.
- may write functional code only; must not edit truth docs or truth routing while realizing those docs.
Progressive disclosure:
- support/procedure.md — read before edits or detailed auditing; contains core review questions
- support/report-template.md — read before the final report
What ships with it
3 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.
- 6d ago First seen · 21 lines · 60 tokens per session scan A f5a2e0684c9f
truthmark-realize is a skill published in the GitHub repository merlinhu1/truthmark (88 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 247 once invoked, about $0.0003 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-design
Design the UI — wireframes, component specs, and design tokens — with a sign-off gate.
amby-plan
Produce the technical implementation plan (the HOW) from an approved spec and UI.
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.