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 agentmods add commands/chappygo-os/atomic-spec/_registry-protocolgit clone --depth 1 https://github.com/Chappygo-OS/Atomic-SpecWhat 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 | $0.00000 | $0.01728 |
| Opus 5 | $0.00000 | $0.00864 |
| Sonnet 5 | $0.00000 | $0.00346 |
| Haiku 4.5 | $0.00000 | $0.00173 |
Grade A, and why
_registry-protocol 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 2d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Defaults Registry Protocol
This protocol is MANDATORY for ALL commands, agents, and phases.
The registry at specs/_defaults/registry.yaml is the single source of truth for project-wide technical decisions. You MUST follow this protocol to ensure consistency.
On Entry (Before Any Work)
Step 1: Load Registry
Read: specs/_defaults/registry.yaml
If file doesn't exist, warn user:
⚠️ No project defaults registry found at specs/_defaults/registry.yaml
Consider running project initialization or creating defaults manually.
Proceeding without defaults - all decisions will be feature-specific.
Step 2: Filter to Your Domain
Only extract sections relevant to your current work:
| If you're working on... | Read these sections |
|---|---|
| Backend / API | api, backend, database |
| Frontend / UI | frontend, ui_specs, conventions |
| Infrastructure / DevOps | infrastructure, testing |
| Full-stack feature | All sections |
Step 3: Apply Defaults
When generating specs, plans, or code:
- Pre-populate fields from registry values
- Mark registry-sourced values with comment:
# from: _defaults/registry.yaml - Never silently use a different value than what's in registry
During Work (Decision Detection)
Scenario A: Decision EXISTS in Registry
Action: Use it. No question. No deviation without explicit approval.
Example:
# Registry has:
api:
versioning: url
# Your spec/plan MUST use:
API Versioning: url-based (/api/v1/*) # from: _defaults/registry.yaml
Scenario B: Decision NOT in Registry (null or missing)
Action: Check if it's a project-wide concern, then ask.
-
Determine scope:
- Project-wide: Would other features benefit from this same choice?
- Feature-specific: Only relevant to this particular feature?
-
If project-wide, use
AskUserQuestion:
┌─────────────────────────────────────────────────────────────┐
│ 📋 NEW PROJECT DEFAULT DETECTED │
├─────────────────────────────────────────────────────────────┤
│ Key: api.pagination │
│ Proposed value: cursor │
│ Context: Decided during billing feature planning │
│ │
│ This appears to be a project-wide decision. │
│ Future features would benefit from consistency here. │
├─────────────────────────────────────────────────────────────┤
│ Options: │
│ ○ Add to project defaults (all features will use this) │
│ ○ Keep as feature-specific (only this feature) │
│ ○ Reject (don't use this value) │
│ ○ Other... │
└─────────────────────────────────────────────────────────────┘
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.
- 2d ago First seen · 245 lines · 0 tokens per session scan A bbe10cba03da
_registry-protocol is a command published in the GitHub repository Chappygo-OS/Atomic-Spec (10 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,728 tokens. 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 commands, from other repositories
taskstoissues
基于现有设计制品，将任务转换为可执行、带依赖顺序的 GitHub Issues。.
cross-critique
Adversarial multi-angle critique. All three auditors fire in parallel (codex=technical, gemini=strategic, claude=ux). Counter-args ranked by rebuttal survival score, not raw severity. Usage: /cross-critique [--with | list | compare].
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
ijfw
IJFW command index. Groups commands by intent: Build / Remember / Ship / Review / Configure.
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].
full-review-gate
Perform a comprehensive repository code review in an isolated worktree. Fix P0/P1 findings and ship them as a PR targeting the current branch.