Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/XAIHT/Tlamatininpx agentmods add skills/xaiht/tlamatini/tlamatini_flw_doctorWrote 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_flw_doctor)<a href="https://agentmods.dev/skills/xaiht/tlamatini/tlamatini_flw_doctor"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/tlamatini_flw_doctor/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_flw_doctor"><img src="https://agentmods.dev/badge/skills/xaiht/tlamatini/tlamatini_flw_doctor.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.00038 | $0.01673 |
| Opus 5.5 | $0.00015 | $0.00669 |
| Sonnet 5.5 | $0.00008 | $0.00335 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade A, and why
tlamatini-flw-doctor 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 today.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.flw doctor
Current release: v1.91.1. Dated records below retain their original evidence dates.
HEADLESS IS FORBIDDEN. VISIBLE FOREGROUND EXECUTION ONLY. Every command, automated test, diagnostic, script, build, agent and browser must run in a visible foreground window on Angela's real desktop. Use forked CMD/PowerShell windows,
execute_forked_window: true, andheadless: false. Monitor live; if visibility cannot be confirmed, do not run. Read the mandatory execution policy.
Statically validate a .flw workflow against the current schema. This is a
read-only diagnostic: it reports findings and never writes a pool
config.yaml, never rewrites the flow, and exits cleanly even when the flow is
broken — the finding IS the deliverable.
The schema you are validating (schemaVersion 2)
⚠️ Do not look for version / agents / from / to. That shape is
obsolete; agent/services/flow_spec.py::normalize_flow_payload is the
authority and it reads:
| key | meaning |
|---|---|
schemaVersion |
integer; 2 is current. Treat anything else as a NAMED finding (unknown_schema_version), not as a parse failure. |
nodes[] |
id, text (the agent display name), left, top, agentPurpose, configData |
connections[] |
sourceId/targetId or sourceIndex/targetIndex, plus inputSlot / outputSlot |
artifacts |
object; artifacts.parametrizerMappings is keyed by node id |
A connection may address its endpoints by id or by index — accept both.
An index outside 0..len(nodes)-1 is a finding (bad_index); a normalizer
would silently DROP that connection, which is exactly the class of defect
this doctor exists to surface.
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.
- today Changed 3895bf0e1cb9
- 4d ago Changed a52d9232a1c2
- 5d ago Changed 5a31ce9f9483
- 7d ago Changed e5bdcfb2389e
- 8d ago Changed 2b55cb85c81d
- 10d ago Changed · +3 lines 3ca6e23980a1
- 1mo ago Changed · +58 lines 867c4124eb67
- 1mo ago Changed · +8 lines 3d9fad0e4e93
- 1mo ago First seen · 62 lines · 38 tokens per session scan A 49d68316f4e9
tlamatini-flw-doctor is a skill published in the GitHub repository XAIHT/Tlamatini (15 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,673 once invoked, about $0.0002 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
cvm-ai-doctor
A health-diagnosis workflow for servers, computers, virtual machines, and containers on Linux, macOS, or Windows.
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
nightly-audit-engineer-getting-started
A first-conversation guide for setting up a code-audit assistant. A code audit is a focused review of source code for defects or risky behavior, with the needed repository, scope, concerns, permissions, and schedule clarified first.
nightly-audit-engineer-ops
A workflow for reviewing code for reproducible quality problems and recording the evidence behind each finding. It follows data through inputs, permissions, storage, asynchronous work, and recovery, then suggests the smallest authorized fix.
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
nightly-audit-engineer-evidence
A small local checker that creates stable identifiers for code-audit findings and marks duplicates within the current batch or among previously seen findings. It processes supplied JSON with Python and does not infer whether a problem was fixed.