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 albiol2004/trio-agent-loop --skill trio-bridgegit clone --depth 1 https://github.com/albiol2004/trio-agent-loopWrote 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/albiol2004/trio-agent-loop/trio-bridge)<a href="https://agentmods.dev/skills/albiol2004/trio-agent-loop/trio-bridge"><img src="https://agentmods.dev/badge/skills/albiol2004/trio-agent-loop/trio-bridge.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.00023 | $0.01248 |
| Opus 5 | $0.00012 | $0.00624 |
| Sonnet 5 | $0.00005 | $0.00250 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
trio-bridge 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the orchestrator of a read-only background scan. You do no scanning or editing yourself — you dispatch scout subagents to find candidate work, dedupe their findings, write proposal cards, and report a short summary. One invocation = one scan pass; re-running is safe (idempotent). You never start loops and never edit project code.
Project root: the current working directory. Every path below is relative to it.
0. Preflight
- Create
proposals/at the project root if it does not exist. - List existing cards:
proposals/*.md. Their frontmatterfingerprintvalues are the dedupe set. - List live missions: every
loop*/GOAL.mdwith amission:line. Work already claimed by a live mission is out of scope.
1. Dispatch scouts (background, parallel)
Dispatch 1-3 read-only trio-scout subagents as background tasks, in parallel, each with a disjoint area or lens (e.g., docs; manifests/checks; code hygiene). The task item MUST name the trio-scout agent and MUST run in the background so nothing blocks on them. Prompt each scout with:
- a READ-ONLY mandate (inspect only; never edit, never run state-changing commands),
- its scan area, and
- the candidate categories to look for: stale or contradictory documentation; manifest/config drift; failing or missing checks; TODO/FIXME clusters; missing verification for recent changes,
- the return contract: a concise list of candidate objects, exactly
{origin, summary, evidence, confidence, class}:origin: the file/path the finding points at,summary: one sentence naming the concrete problem (deterministic wording — it feeds the fingerprint),evidence:file:linereferences or the exact failing command,confidence: low | medium | high,class: A | B | C (definitions in step 4),
- no prose and no file contents in the reply — only the list.
Scout results auto-deliver in the background; never busy-poll and never block your turn waiting for them.
2. Collect
Read ONLY the scouts' concise candidate lists. The list IS the entire handoff — never read the scanned files into your context. If a scout returns raw file dumps instead of the list, discard the dump and re-dispatch once with the list format re-stated.
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.
- 7d ago First seen · 88 lines · 23 tokens per session scan A e7f4e1ff593b
trio-bridge is a skill published in the GitHub repository albiol2004/trio-agent-loop (2 stars, last pushed 7d ago), licensed MIT. It adds 23 tokens to every session and 1,248 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-31.
Other skills, from other repositories
taiyi-design
A technical-design guide for planning software changes before implementation. It produces a DESIGN.md document comparing at least two approaches and recording the chosen structure and trade-offs.
taiyi-plan
A TaiyiForge planning step that turns a README, product requirements document, or technical plan into a list of separate project changes. Each change includes a suggested work profile, dependencies, and priority.
taiyi-dev
A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.