Borrowing it
Nothing to install: this file belongs to katopz/katgpt-rs. 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/katopz/katgpt-rs/develop/.agents/skills/substrate-first/SKILL.mdgit clone --depth 1 https://github.com/katopz/katgpt-rsWrote 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/katopz/katgpt-rs/substrate-first)<a href="https://agentmods.dev/skills/katopz/katgpt-rs/substrate-first"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/substrate-first/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/katopz/katgpt-rs/substrate-first"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/substrate-first.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.00159 | $0.14685 |
| Opus 5.5 | $0.00064 | $0.05874 |
| Sonnet 5.5 | $0.00032 | $0.02937 |
| Haiku 4.5 | $0.00016 | $0.01469 |
Grade A, and why
substrate-first 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 today.
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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Substrate-First — DRY gate + drift audit
The workspace — 18 repos carrying a root BOUNDARY.md as of 2026-09-01,
derived by the snippet in Step 2 rather than typed here — has a recurring
failure mode: an agent receives a task
("add threat perception"), jumps to implementation without checking existing
substrate, and builds a parallel system that duplicates functionality
already shipped under a different name. The user then has to catch it manually.
This skill prevents that. It runs in two modes:
- Pre-implementation gate — run BEFORE writing code
- Existing-code audit — scan for already-shipped DRY violations
Canonical failures (the pattern this skill prevents)
Failure 1 — ThreatField (Issue 047, riir-mmorpg-examples, 2026-08-01)
Built: ThreatField — a spatial hash grid (HashMap<(i32,i32), u32>)
for threat perception. Deposited monster positions into cells; NPCs sampled
the 3×3 neighborhood.
Already existed: GenericSpatialBelief<T> + target_within_visible_radius()
decay_confidence()— the full fog-of-war → belief → decay pipeline inriir-games-shared/src/game_traits/spatial.rs.
Why the grep missed it: The agent searched for "threat field" /
"spatial hash". The substrate ships as GenericSpatialBelief /
SpatialBelief / confidence_decay. A single-vocabulary grep returns
ZERO hits even when the substrate fully exists.
Resolution: Reverted. The plain scan (tick_swarm_emotions) is a simpler
POC-scale simplification. The belief-based system is deferred until fog-of-war
becomes a gameplay feature.
Failure 2 — Orchard + Motivation in SDK src/ (Issue 490 + Issue 493)
Built: NpcReasonSystem, AppleGrowSystem, OrchardGoal, EmotionField,
EmotionAxis, tick_feeling_brain directly in the SDK facade's src/.
Already existed: The boundary rule (riir-game-sdk/AGENTS.md) says "no game
logic in src/" + Proposal 019 excludes emotion from the SDK. The substrate
belongs in riir-games (in riir-ai).
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.
- today Changed · +11 lines 2f8d2a8deace
- yesterday Changed · +2 lines 9feaeb208e06
- 3d ago Changed cd23c3285722
- 4d ago Changed 0f64adc4edc7
- 5d ago Changed · -3 lines b171d8bf1f2a
- 7d ago Changed · +1 lines c1109d70075c
- 9d ago Changed · +2 lines d441fed0fcf4
- 11d ago Changed · -4 lines 2eda0e6063ed
- 12d ago Changed · +2 lines 7aa860dd1ae3
- 14d ago First seen · 390 lines · 159 tokens per session scan A dfe69d8db73d
substrate-first is a skill published in the GitHub repository katopz/katgpt-rs (140 stars, last pushed today), licensed MIT. It adds 159 tokens to every session and 14,685 once invoked, about $0.0006 per session on Opus 5.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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…