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 chrono-meta/forge-harness --skill agent-composergit clone --depth 1 https://github.com/chrono-meta/forge-harnessWrote 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/chrono-meta/forge-harness/agent-composer)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/agent-composer"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/agent-composer.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.00074 | $0.06261 |
| Opus 5 | $0.00037 | $0.03130 |
| Sonnet 5 | $0.00015 | $0.01252 |
| Haiku 4.5 | $0.00007 | $0.00626 |
Grade C, and why
agent-composer scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| File/data destruction | rm -rf, DB DROP/DELETE, file overwrite, branch delete | How it starts
The opening of the file, as written. The whole thing — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-composer — Agent Composition Layer
A coordinator skill that reads the work context and decides "which agents to dispatch, when, and in what order." Selects the optimal combination from the FH skill pool and either outputs a fan-out plan or executes it directly.
Triggers
/agent-composer- "Which agent should I use?", "Pick one automatically", "Compose the agents"
- "Set up the agents", "Decide which agents to use"
- "Split the work and run in parallel", "Process with multiple agents"
- "Build the dispatch plan", "Run in parallel splits"
- When the task is complex or spans multiple projects
Core Principles
- Compose only: Does not perform work directly. Outputs the dispatch plan and executes after user approval.
- Parallel first: When 2+ tasks are independent, propose parallel fan-out instead of sequential.
- Minimal composition: Only the agents needed. Over-provisioning agents creates inefficiency.
- Coordinator ≠ executor: Only collects results (fan-in) and presents an integrated report.
Step 0. Context Collection
Identify 4 items from the request: task type · scope · constraints · natural-language goal → skill mapping.
Check LOCAL_SKILL_REGISTRY.md for project-local skills; check .mcp.json or CLAUDE.md for external plugins.
Detail: See
SKILL_detail.md §Step-0— NL pattern mapping table, cross-install detection, registry lookup format — read when auto-mapping an ambiguous request.
Step 0.2 — Capability Fit Analysis
Schema:
knowledge/shared/harness-core/tpa_schema.md—artifact_typeenum determinesrole_matchlookup domain for scoring. Runs before dispatching agents. Skip if user specifies exact agents by name.
For each subtask in the composition plan:
- Read agent registry:
.claude/agents/*.md+ installed plugin agents
Extract:role·allowed_tools·writes·declared_capabilities - Score capability fit:
[subtask_type]×[agent capabilities]→fit_score(0.0–1.0) - GAP:
fit_score < 0.5for a required-weight subtask
→ query/plugin-recommender: "agent for [subtask_type] in [context]"
→ includes Codex marketplace + Claude Code marketplace (not just FH native)
→ user: install / skip / use general-purpose fallback
What ships with it
1 file 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.
- 8d ago First seen · 515 lines · 74 tokens per session scan C 81bbcf79d2f3
agent-composer is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 6,261 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
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-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-compress
A workflow tool for shrinking large coding-agent conversations and work files into shorter context notes. It can also coordinate separate agents for parallel development and create handoff notes for continuing work in a new session.