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 asfbay-bit/opchain-skills --skill oc-agent-forgegit clone --depth 1 https://github.com/asfbay-bit/opchain-skillsWrote 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/asfbay-bit/opchain-skills/oc-agent-forge)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-agent-forge"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-agent-forge/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/asfbay-bit/opchain-skills/oc-agent-forge"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-agent-forge.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.00102 | $0.07074 |
| Opus 5 | $0.00051 | $0.03537 |
| Sonnet 5 | $0.00020 | $0.01415 |
| Haiku 4.5 | $0.00010 | $0.00707 |
Grade A, and why
oc-agent-forge scanned grade A 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Bash vs dedicated tool | Bash for breadth, promote to gate/render/audit | A dedicated `send_email` tool can be confirmation-gated; `bash -c curl` can't | How it starts
The opening of the file, as written. The whole thing — 554 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Forge
On first invocation, read references/orchestrator.md and follow its welcome protocol (if present; otherwise fall back to the shared skills/orchestrator.md).
Tri-agent build harness for Claude Agent SDK apps: the Planner decides the agent topology (single-agent vs orchestrator-worker vs pipeline vs hierarchical), the tool budget, and the harness loop shape → the Builder materialises the harness, tool allowlist, and termination logic against the Claude Agent SDK → the Evaluator runs the agent against a task fixture suite with isolated context and gates it on task-success / trajectory / tool-efficiency thresholds.
An agent is not "give the model some tools and a while-loop." Every default — how many subagents, which tools are in the allowlist, when the loop stops, how much context is carried turn-to-turn — moves a measurable number: task success, token cost, tool-call count, or wall-clock latency. The only honest way to set those defaults is to run the agent against fixtures and score the trajectory. This skill exists to make the agent harness an evaluated artifact, not a vibe.
This is the agent-harness counterpart to oc-claude-api. Model routing — which
model runs the orchestrator, which runs a worker, effort levels, prompt caching,
thinking mode — comes FROM oc-claude-api. Agent Forge owns the layer above the
model: topology, tool budget, loop shape, and the eval. The two skills compose;
they do not overlap.
/oc-agent — Command Reference
AGENT FORGE COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TRI-AGENT HARNESS
/oc-agent Design + build an agent end-to-end (Planner → Builder → Evaluator)
/oc-agent plan Pick topology, tool budget, loop shape (Planner)
/oc-agent build Materialise the harness + tool allowlist (Builder)
/oc-agent eval Score the agent against a task fixture suite (Evaluator)
HARNESS DESIGN
/oc-agent topology Choose single-agent / orchestrator-worker / pipeline / hierarchical
/oc-agent tools Design the tool allowlist + call ceilings + deferred-load
/oc-agent loop Design / tune the harness loop (react / plan-execute / reflect)
EVALUATION
/oc-agent fixtures Build or extend the task fixture suite (input → expected outcome)
/oc-agent trace Replay one fixture and dump the full trajectory (debug)
/oc-agent regress Re-run the fixture suite and gate on success/cost regression
UTILITIES
/checkpoint Show checkpoint status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command to begin. /oc-agent to see this again.
What ships with it
6 files 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.
- 6d ago Changed b91670793b3e
- 9d ago First seen · 554 lines · 102 tokens per session scan A 503251eec3aa
oc-agent-forge is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 102 tokens to every session and 7,074 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.