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/project-profile)<a href="https://agentmods.dev/commands/srnichols/plan-forge/project-profile"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/project-profile/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/project-profile"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/project-profile.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.00022 | $0.01335 |
| Opus 5 | $0.00011 | $0.00668 |
| Sonnet 5 | $0.00004 | $0.00267 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
project-profile 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Profile Generator
When to use: Once per project (during or after setup), then update as the project evolves
Output:.github/instructions/project-profile.instructions.md
Relationship: Supplements (does not replace)architecture-principles.instructions.md
Act as a PROJECT PROFILE GENERATOR. Interview me about this project's specific quality standards, constraints, and domain rules. For each category below, I've noted the universal baseline that already ships with the architecture principles. Ask me if I want to:
- Accept the default (baseline is fine for this project)
- Tighten it (stricter than baseline for this project)
- Add project-specific rules (new rules not in the baseline)
After the interview, generate a .github/instructions/project-profile.instructions.md file with only the categories where I've customized or added rules. Skip categories where I accept the defaults — the universal baseline already covers those.
Category 1: Code Quality
Universal baseline (always active):
- No
any(TypeScript) / Nodynamic(C#) / NoAny(Python) when type is known - Explicit types on function signatures
- Use generics over type assertions
- No empty catch blocks — always log or handle
Ask me:
- Any additional banned patterns? (e.g., no default exports, no magic numbers)
- Stricter lint rules beyond the baseline?
- Documentation requirements? (e.g., JSDoc on public methods, XML docs)
Category 2: Testing
Universal baseline (always active):
- TDD for business logic: Red → Green → Refactor
- Integration tests for data access
- E2E tests for critical user flows
Ask me:
- Coverage target? (e.g., 80%, 90%, or no enforced target)
- Which test frameworks does this project use?
- Required test types beyond unit/integration/E2E? (e.g., contract tests, load tests, mutation tests)
- Any specific testing patterns? (e.g., test containers, in-memory databases)
Category 3: Performance
Universal baseline (always active):
- All I/O operations must be async
- Never block on async operations
- Support cancellation where the platform provides it
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 First seen · 149 lines · 22 tokens per session scan A 661c6dd20796
project-profile is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,335 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
init-workspace-flow-discovery
Phase 3 Discovery of init-workspace-flow.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
ui-aqa-flow-code-analysis
Phase 3 Code Analysis of ui-aqa-flow.
adhoc-flow
Workflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.