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.
git clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/commands/srnichols/plan-forge/new-org-rules)<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-org-rules"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-org-rules/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/commands/srnichols/plan-forge/new-org-rules"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-org-rules.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.00013 | $0.00414 |
| Opus 5 | $0.00006 | $0.00207 |
| Sonnet 5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
new-org-rules 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 yesterday.
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
Initialize Org-Specific Azure Rules
Create a populated org-rules.instructions.md from the org-rules template, with your organisation's actual values.
Steps
- Read
.github/instructions/org-rules.instructions.md.template - Read any existing project files that reveal org standards:
README.md,CUSTOMIZATION.md, existing Bicep/Terraform naming patterns- Pipeline YAML for region, subscription, environment hints
- Ask the user for any values not found in existing files
- Write the completed
.github/instructions/org-rules.instructions.md
Questions to Ask
Before generating, gather:
- Tenant ID and primary subscription ID?
- Approved Azure regions? (influences naming, data residency)
- Workload abbreviations? (team code + workload short names)
- Compliance frameworks required? (ISO 27001, SOC 2, GDPR, HIPAA, PCI-DSS)
- Monthly budget per subscription? (for cost guardrail)
- Key contacts? (platform team, security, finops emails)
- Data classification levels used? (keep default or customise)
- Required extra tags? (beyond CAF mandatory set)
Rules
- REPLACE every
<!-- ... -->placeholder — leave none behind - Do NOT invent values for security-sensitive fields (tenant ID, subscription ID, CIDR ranges) — ask the user
- Keep the frontmatter
applyTopattern — it controls auto-load scope - After writing, confirm with user that values are correct before committing
Reference Files
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.
- yesterday First seen · 44 lines · 13 tokens per session scan A 4478bff5db8b
new-org-rules is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 414 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-09-08.
Other commands, from other repositories
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
modernization-flow-review
Phase 7 Review of modernization-flow.
init-workspace-flow-questions
Phase 8 Questions of init-workspace-flow.