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 agentmods add skills/chrono-meta/forge-harness/sim-conductornpx skills add chrono-meta/forge-harness --skill sim-conductorgit 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/sim-conductor)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/sim-conductor"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/sim-conductor.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.00065 | $0.08111 |
| Opus 5 | $0.00032 | $0.04056 |
| Sonnet 5 | $0.00013 | $0.01622 |
| Haiku 4.5 | $0.00006 | $0.00811 |
Grade A, and why
sim-conductor 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 5d 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 — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sim-conductor — Meta-Simulation Automation Orchestrator
Profiles target → derives personas → dispatches parallel agents → M/S/R triage → commit. Personas are sourced installed-first → filled from the persona-container schema (7 slots as of 2026-07-18 — stance added, not an ad-hoc directive) → external install. Scale: 3 to 16, extensible to a crowd behind the marginal-coverage stop (§Scale).
Invocation Triggers
| Trigger pattern | Suggested Area |
|---|---|
| "Look at this from an external user's perspective", "How would someone else see this?" | Area A |
| "Check the harness", "asset audit", "internal audit" | Area B |
| "Any new ideas?", "ideation scan", "naming candidates" | Area C |
| "Review this code" (pre-PR), "review this prompt" | Area D (code) |
| "Check if the session card is correct", "does the skill actually work", "memory cold-start validation" | Area D (consumer) |
| "Is the output good?", "artifact quality review" | Area E |
Proposal format: "If it's related to [X], should I simulate with /sim-conductor [Area]?"
Natural Language Triggers
| Example utterance | Intent | Mapped Area |
|---|---|---|
| "Validate our system virtually" | Full system simulation | Area B |
| "Test it with personas", "Run an external user simulation" | External user reaction | Area A |
| "Look at it through someone else's eyes" | External perspective | Area A |
| "Validate that this actually works" | Real-usage validation | Area D |
| "Find problems aggressively" | Adversarial validation | Area B (challenger) |
Triggers
/sim-conductor # default: Area C auto-run
/sim-conductor A # external user simulation
/sim-conductor B # internal meta audit
/sim-conductor C # Innovator scan
/sim-conductor all # full A + B + C
/sim-conductor A --target <path> # specific asset target
/sim-conductor D --target <file> # code/prompt multi-persona review (pre-PR)
/sim-conductor D session [--target] # session card cold-start validation
/sim-conductor D skill <name> # skill trigger utterance consumer simulation
/sim-conductor D memory <file> # memory file cold-start validation
/sim-conductor E --target <file> # artifact quality review (post-pipeline)
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.
- 5d ago First seen · 567 lines · 65 tokens per session scan A 106fe917bd7f
sim-conductor is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 8,111 once invoked, about $0.0003 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
reconcile
Cross-reference a paper against the collection. Finds which cited papers are already collected, which are new leads, which collection papers cite this one, and reconciles all cross-references bidirectionally. Run on a single paper directory or use --all for the entire collection.
adjudicate
Systematically adjudicate disagreements across a paper collection. Produces ruthless verdicts on who was wrong, what supersedes what, and what the best current understanding is. Organized by topic clusters with actionable replacement values for implementation.
author-context
Create a propstore context for one paper with CEL assumptions, parameters, and perspective. Every claim extracted from the paper will reference this context. Required before extract-claims if the paper does not already have one.
author-lifting-rules
Author DeLP/McCarthy context lifting rules between existing context YAMLs so cross-context claim reasoning can proceed. Collection-level, runs after all papers are ingested. Targets the CONTEXTPHINODE records that accumulate when multiple per-paper contexts share concepts with no authored bridges.
author-rules
Author the DeLP rule artifacts (strict, defeasible, properdefeater, blockingdefeater) encoding a paper's stated argument structure. Runs after register-predicates.
extract-claims
Extract propositional claims from a paper directory into the propstore source branch using pks source propose-claim.