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 XAIHT/Tlamatini --skill tlamatini_planner_trace_replaygit clone --depth 1 https://github.com/XAIHT/TlamatiniWrote 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/xaiht/tlamatini/tlamatini_planner_trace_replay)<a href="https://agentmods.dev/skills/xaiht/tlamatini/tlamatini_planner_trace_replay"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/tlamatini_planner_trace_replay/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/xaiht/tlamatini/tlamatini_planner_trace_replay"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/tlamatini_planner_trace_replay.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.00034 | $0.00503 |
| Opus 5 | $0.00017 | $0.00251 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
tlamatini-planner-trace-replay 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.
What it actually says
Planner trace replay
Read the tail of Tlamatini/tlamatini.log. Locate the most recent
build_global_execution_plan invocation and the per-capability scoring
output.
For each capability the planner scored:
- record its score and the keywords that contributed
- record whether it was selected (top-N cap, see
max_selected_tools = 20per gotchas.md #11) - if a capability that "should" have been selected was not, explain why
Return { traces: [...], notes }. Keep traces under 32 KB total to
preserve context.
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 · 55 lines · 34 tokens per session scan A 97c296988151
tlamatini-planner-trace-replay is a skill published in the GitHub repository XAIHT/Tlamatini (16 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 503 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
review
Review current code changes for bugs, regressions, test gaps, and project-guideline violations.
grade-and-fix-daedalus
How to grade a Daedalus run (or pasted agent transcript), root-cause the failure, and ship the fix to Daedalus CORE as a stacked PR — without modifying the prompt-vault sandbox (read-only grading). Covers recurring bug archetypes (Unicode punctuation patch mismatch, syntax-vs-type mislabel, emoji box misalignment…
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…