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.
git clone --depth 1 https://github.com/tma1-ai/tma1Wrote 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/commands/tma1-ai/tma1/tma1-search)<a href="https://agentmods.dev/commands/tma1-ai/tma1/tma1-search"><img src="https://agentmods.dev/badge/commands/tma1-ai/tma1/tma1-search/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/commands/tma1-ai/tma1/tma1-search"><img src="https://agentmods.dev/badge/commands/tma1-ai/tma1/tma1-search.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.00017 | $0.00470 |
| Opus 5 | $0.00009 | $0.00235 |
| Sonnet 5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
tma1-search 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 12d 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
TMA1 Session Search — /tma1-search
Full reference lives in skills/tma1-search/SKILL.md.
Parse $ARGUMENTS
--session <id>→ skip search, callmcp__tma1__get_session_transcriptwith that id (full id or 6+ character prefix). Never guess an id from a bare token — commit hashes andoc:/cp:ids are indistinguishable from one.- Everything that isn't a flag →
query. --agent X→agent_source(codex·openclaw·copilot→copilot_cli·claude/cc→claude_code·self). Omit for every agent.--days N→since_min = N × 1440. Omit for the 7-day default.--all-projects→project: "*". Omit to stay in the current project.- No query and no
--session→ ask what to search for. Don't call the tool.
Then
mcp__tma1__search_sessions→ report matches with their snippets.mcp__tma1__get_session_transcripton the chosensession_id. Ifhas_moreis true and the answer isn't in the page, call again withnext_offset.- Answer by quoting the earlier session, not by summarising it.
Read match_mode before presenting results: substring means the
indexed word-boundary search (which is case-sensitive) found nothing, so
the query was widened to a case-folded substring scan. Say so.
Empty results carry a note; report the silence rather than inventing a
session.
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.
- 12d ago First seen · 37 lines · 17 tokens per session scan A ee86d468e9e3
tma1-search is a command published in the GitHub repository tma1-ai/tma1 (118 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 470 once invoked, about $0.0001 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 commands, from other repositories
iai-directive
Record, list, or remove a standing order the user typed themselves.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
tree-ring-status
Check receipt-backed Tree Ring harness readiness without claiming configuration is activation.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.