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 supportersimulator/3-surgeons --skill architectural-gategit clone --depth 1 https://github.com/supportersimulator/3-surgeonsWrote 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/supportersimulator/3-surgeons/architectural-gate)<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/architectural-gate"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/architectural-gate/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/supportersimulator/3-surgeons/architectural-gate"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/architectural-gate.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.00019 | $0.01174 |
| Opus 5 | $0.00010 | $0.00587 |
| Sonnet 5 | $0.00004 | $0.00235 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
architectural-gate 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 8d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architectural Gate
The Core Invariance Skill
This is the primary quality gate for the 3-Surgeons invariance suite. It ensures that no significant change proceeds without proportional scrutiny.
Auto-Invocation Triggers
Invoke this skill when ANY of these signals are present:
| Signal | Examples |
|---|---|
| Architectural decision | New subsystem, data flow change, module restructuring |
| >3 files will change | Multi-file refactor, cross-cutting concern |
| New dependency added | npm/pip package, external service, API integration |
| Security-sensitive code | Auth, crypto, input validation, secrets handling |
| Database schema change | Migration, new table, index change, column alter |
| API surface change | New endpoint, modified contract, breaking change |
| Config/infrastructure change | Docker, CI/CD, env vars, deploy config |
If even ONE signal is present, this gate fires.
Risk Stratification
Not all changes need full gating. The gate assesses risk across multiple dimensions and selects a proportional mode:
Risk Dimensions (multi-axis, not scalar)
| Dimension | Low | Medium | High |
|---|---|---|---|
| Blast radius | 1 file | 2-5 files | >5 files |
| Reversibility | Easy rollback | Moderate effort | Hard/impossible |
| Security exposure | No auth/crypto | Touches validation | Auth/crypto/secrets |
| Data impact | Read-only | Schema additive | Schema destructive |
| External coupling | No new deps | New internal dep | New external service |
Mode Selection
| Mode | When | What Runs | Target Time |
|---|---|---|---|
| Light | All dimensions Low. Single-file, clear scope, no arch change | Sentinel scan only. If risk=low, proceed. | <30s |
| Standard | Any dimension Medium. 2-5 files, moderate complexity | Sentinel + gains-gate. Cross-exam if sentinel >= medium. | <120s |
| Full | Any dimension High. >5 files, security, schema, new subsystem | Sentinel + cross-exam + counter-position + gains-gate. | <300s |
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.
- 8d ago First seen · 116 lines · 19 tokens per session scan A cb062800026e
architectural-gate is a skill published in the GitHub repository supportersimulator/3-surgeons (2 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,174 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
gh-pr-review
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks…
review-spd
Findings-first code review workflow for AI coding agents. Use when the user asks to review uncommitted changes, commits in a date range, or a branch compared to the main branch / PR-style diff. Focuses on bugs, regressions, correctness risks, missing tests, security/data-safety issues, and other behavior-changing…
karpathy-guidelines
A set of coding guidelines based on observations about common mistakes made by language models. It emphasizes simple solutions, small targeted edits, clear assumptions, and checkable results.
gh-cli
Patterns for invoking the GitHub CLI (gh v2.100.0+) from agents. Use when the task mentions GitHub, gh, pull requests/PRs, issues, releases, gists, Actions/workflow runs, forks, repo cloning, reviews, or you need exact gh commands. Covers pagination, repo targeting, search vs list, discussions, projects, rulesets…
code-review
A single-pass review method for examining a code change, branch, or pull request. A pull request is a proposed change for review before it is merged into a shared codebase.
simplify
Behavior-preserving code simplification — reduce complexity without changing what the code does. Use when the task mentions "simplify", "reduce complexity", "too clever", "hard to read", "reduce nesting", or after a feature lands and the code needs polishing. Oracle analyzes (read-only), light-orchestrator applies the…