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 verify-bidirectionalgit 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/verify-bidirectional)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/verify-bidirectional"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/verify-bidirectional.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.00062 | $0.05421 |
| Opus 5 | $0.00031 | $0.02710 |
| Sonnet 5 | $0.00012 | $0.01084 |
| Haiku 4.5 | $0.00006 | $0.00542 |
Grade A, and why
verify-bidirectional 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-bidirectional — Bidirectional Self-Validation Automation
Automates the processing procedure for bidirectional self-validation. Three stages: user counter-argument → baseline update → next session reflection.
Trigger Conditions
Immediately after this harness AI recommendation/agreement/decision is committed, when the user raises a refinement challenge:
- Proposition refinement: "isn't it more like..." / "I'd say..." / "what about this" / "what's the root?"
- Baseline grep trigger: User cross-references own assets, memory, CLAUDE.md rules, past decisions
- Meta-level trigger: "if you have objections" / "double-check" / "essence" / "root cause"
- Side validation result: User runs independent tools (
/skills·gh· external fetch) → catches mismatch with this harness AI hypothesis
Natural Language Triggers (works without internal vocabulary)
Also triggered in external user environments by these natural language phrases:
| Phrase | Intent |
|---|---|
| "is that right?", "re-examine this" | Request AI recommendation re-validation |
| "something seems off", "this doesn't feel right" | Counter-argument / refinement |
| "I think you said something different before" | Catch inconsistency with past decisions |
| "can you be more precise?" | Proposition refinement trigger |
| "what's your basis?", "why do you think that?" | Baseline grep trigger |
| "check that one more time" | Self-validation request |
🟥 5. Prescriptive doctrine statement — the category that fell through (added 2026-08-16)
Every trigger above is shaped as doubt about a claim. A large class of operator correction is not doubt at all — it is a standing rule being handed over, stated as fact or instruction:
| Shape | Real examples (2026-08-16 session) |
|---|---|
| "X should also include Y" | "입장리뷰에는 정적리뷰뿐만 아니라 동적리뷰도 포함되어야 할 거야" |
| "the real point of X is Z" (redefining, not doubting) | "부스팅보다 인큐베이터의 장점은 그 레포 전체를 감싸서 …모든 것을 조작할 수 있는 권한이 있는 거야" |
| "isn't this too late / wrong-ordered?" (rhetorical, expects agreement) | "이 실패가 CI 확인 단계에서야 발견되는 건 매우 늦은 게 아닐까" |
| "from now on, do W at Z" | "앞으로도 마감할 때 그 갈래로 이어갈 수 있게 알아서 정리해줘" |
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 · 353 lines · 62 tokens per session scan A 0ffd3eceb032
verify-bidirectional is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 5,421 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
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.
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…
remem
Use when the user asks Codex to recall prior project context, save durable decisions or bug fixes, inspect remem memory health, or activate remem automatic memory hooks from the Codex plugin.
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…
memory
Use when user invokes /memory with a subcommand (search, trace, add, episode, status). Also triggers on "search my memory for X", "add to memory", "what do I know about X" (when membrain is available), "memory status", "memory trace". Searches and manages the membrain knowledge graph via MCP tools or HTTP API.
capture
Use when user invokes /capture to capture information from the current conversation into a staging file for later reflection and knowledge graph processing. Accepts no arguments (auto-extract), specific facts as text, or filter keywords like "decisions" or "technical". Do NOT use when the user wants to write directly…