Borrowing it
Nothing to install: this file belongs to ontorata/ratary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ontorata/ratary/main/.cursor/skills/forge-prove/SKILL.mdgit clone --depth 1 https://github.com/ontorata/rataryWrote 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/ontorata/ratary/forge-prove)<a href="https://agentmods.dev/skills/ontorata/ratary/forge-prove"><img src="https://agentmods.dev/badge/skills/ontorata/ratary/forge-prove.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.00026 | $0.00261 |
| Opus 5 | $0.00013 | $0.00130 |
| Sonnet 5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
forge-prove 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.
What it actually says
Forge Prove
Activates: during forge-execute when behavior changes.
Cycle
- Red — write or extend a test that fails for the right reason
- Witness — run test; confirm failure message matches intent
- Green — minimal production code to pass
- Witness — full relevant suite passes
- Refactor — only with green tests; no scope expansion
Anti-patterns (reject)
- Production code before any failing test (unless pure refactor with full coverage)
- Tests that always pass regardless of implementation
- Deleting tests to go green
skip/@ts-ignoreto bypass without owner OK
Commands
npm test -- path/to/focused.test.ts
npm test # before task complete
Prompt cross-ref
docs-ai/cross-cutting/agent-forge/workflow/prompts/testing/unit-test-design.md
When to skip
Docs-only or comment-only — run lint/typecheck instead.
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 · 40 lines · 26 tokens per session scan A 116f87001274
forge-prove is a skill published in the GitHub repository ontorata/ratary (1 stars, last pushed 28d ago), licensed MIT. It adds 26 tokens to every session and 261 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.