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-inspect/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-inspect)<a href="https://agentmods.dev/skills/ontorata/ratary/forge-inspect"><img src="https://agentmods.dev/badge/skills/ontorata/ratary/forge-inspect.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.00025 | $0.00380 |
| Opus 5 | $0.00013 | $0.00190 |
| Sonnet 5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
forge-inspect 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 Inspect
Activates: between forge-execute tasks (and before land).
Two passes
Pass 1 — Spec compliance
- Diff matches current blueprint task only
- ADR / phase requirements satisfied
- No forbidden patterns (11-AI-RULES.md Never create)
- Inspection Pattern Ledger (Phase 8.8): recall relevant ledger entries via MCP
search_memorytaginspection-patternor REST/api/v1/inspection-patterns?path=…— use as prioritized checklist only; constitutional blockers still come from spec, not ledger alone
Pass 2 — Code quality
- Layer boundaries (no transport in services)
- Matches .ai/core/standards/02-CODING.md
- Tests exist for behavior changes
Severity
| Level | Action |
|---|---|
| constitutional | Block — fix before next task |
| critical | Block — fix before next task |
| major | Fix in current task if small; else add blueprint task |
| minor | Note; optional follow-up |
Output
## Inspect — Task N
- Spec: PASS / FAIL
- Quality: PASS / FAIL
- Blockers: (list or none)
Prompt cross-ref: docs-ai/cross-cutting/agent-forge/workflow/prompts/review/code-review.md
Optional: launch Bugbot subagent for large diffs when user requests.
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 · 47 lines · 25 tokens per session scan A ab2c649934be
forge-inspect is a skill published in the GitHub repository ontorata/ratary (1 stars, last pushed 28d ago), licensed MIT. It adds 25 tokens to every session and 380 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
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.