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/boundary-guard/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/boundary-guard)<a href="https://agentmods.dev/skills/katopz/katgpt-rs/boundary-guard"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/boundary-guard/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/boundary-guard"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/boundary-guard.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.00155 | $0.16152 |
| Opus 5.5 | $0.00062 | $0.06461 |
| Sonnet 5.5 | $0.00031 | $0.03230 |
| Haiku 4.5 | $0.00015 | $0.01615 |
Grade A, and why
boundary-guard 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boundary Guard
Generic game logic → substrate (riir-games). View renders state, doesn't compute it. FFI moves raw bytes only.
Spec source — each repo's BOUNDARY.md
Every repo ships a root BOUNDARY.md — the per-repo
contract this skill audits against: Owns / Does not own / May depend
on (crate-granular allowlist with Location) / Inherited (links) / Drift
ledger. The 8-surface table below is the workspace methodology; the per-repo
rules + exceptions come from that repo's BOUNDARY.md, not from this file's prose.
Findings are therefore two classes: code-vs-contract violations and
contract rot (drift row without an open issue, allowlist row without a gate,
by-design row whose decision record is gone).
Two scripts, one job each (added 2026-08-21, Issue 737 T-CI/T-GATE):
| script | scope | question it answers |
|---|---|---|
riir-ai/scripts/ci_boundary_contract.sh |
workspace (every repo with a root BOUNDARY.md — 18 again since 2026-09-10: 16 after the 2026-09-04 retirements, then +riir-esp32 2026-09-06, +riir-kat 2026-09-10; the script enumerates, so prefer its banner over this cell) |
Is the dep graph what the contracts say — and are the contracts still honest? Parses every May depend on table + drift ledger, checks the riir-ai CANONICAL matrix against the measured graph, pins the 4 split-prep invariants. --list-deps prints the measured edge set; --repo X narrows. |
riir-mmorpg-examples/scripts/ci_boundary_guard.sh |
that repo's src/ |
Is the CODE in the right repo? Checks A–E: System impls with game logic, duplicated geometry, hardcoded behavior constants, generic logic in free functions, facade leaks. |
The contract script replaces prose-only allowlists; it is the successor of
Issue 724 Phase 2's "document the contract and review by hand". EXEMPT_LEAKS
in the per-repo guard deliberately STAYS file-granular — the ledger is
surface-granular, and collapsing the two would lose the file:line precision
Check E needs.
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 · +1 lines 6c9d6b5df6d0
- yesterday Changed · -7 lines 8425d549f34a
- 2d ago Changed · -4 lines dc7216e56897
- 3d ago Changed · +8 lines 0116c4d957b7
- 4d ago Changed · -10 lines 95594704c8aa
- 5d ago Changed · +7 lines 2974fc3d84f9
- 6d ago Changed · +1 lines ac2fa3f22d58
- 8d ago Changed · +1 lines ac9377b4b32c
- 9d ago Changed · +3 lines 45946ab4ff5a
- 10d ago First seen · 193 lines · 155 tokens per session scan A 8193e9524f0c
boundary-guard is a skill published in the GitHub repository katopz/katgpt-rs (140 stars, last pushed today), licensed MIT. It adds 155 tokens to every session and 16,152 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
godot-code-review
Use when reviewing GDScript or C# Godot code — checklist of best practices, common anti-patterns, and Godot-specific pitfalls. Triggers on "review this script", "check my code", "any issues with this", "what's wrong with this code", including a short pasted snippet.
animation-review
Reviews Godot Animation implementation for known pitfalls. Triggers AFTER implementation, when code involves AnimationPlayer, AnimationTree, AnimatedSprite2D, SpriteFrames, AnimationNodeStateMachine, BlendSpace, OneShot, callbackmodeprocess, or animation playback control (play/travel/start). Do NOT use this skill for…
tilemap-review
Reviews Godot TileMap implementation for known pitfalls. Triggers AFTER implementation, when code involves TileMapLayer, TileSet, TileSetAtlasSource, TileSetScenesCollectionSource, terrain painting, setcell, erasecell, getcelltiledata, collision polygons on tiles, or NavigationRegion2D with tile-based navigation. Do…
hz-unity-code-review
Reviews Unity code targeting Meta VR and Horizon OS for performance issues, rendering best practices, and common VR pitfalls. Use during code review or when diagnosing Meta VR performance problems in Unity projects.
code-review
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
design-lenses
Critique a game's design through Schell's lenses, MDA and systems thinking, ranking findings by severity with fixes. Design-level review, not bugs or feel tuning.