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 instructions/srnichols/plan-forge/git-workflowgit clone --depth 1 https://github.com/srnichols/plan-forgeWhat 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.00497 | $0.00497 |
| Opus 5 | $0.00249 | $0.00249 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
plan-forge git-workflow.instructions.md 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
Git Workflow
Applies to: ALL files
AI Agent Instructions
Before Starting Work
"Before we begin, ensure Git state is clean:
1. Pull latest: git pull origin main
2. Check status: git status
3. Stash if needed: git stash"
After Completing Changes
"Changes complete! Commit and push:
1. Stage: git add -A
2. Commit: git commit -m '<type>(<scope>): <description>'
3. Push: git push origin main"
Conventional Commit Format
<type>(<scope>): <short description>
[optional body]
[optional footer]
Commit Types
| Type | When to Use | Example |
|---|---|---|
feat |
New feature | feat(auth): add OAuth2 login flow |
fix |
Bug fix | fix(api): resolve null reference in user lookup |
perf |
Performance improvement | perf(queries): add index for tenant lookups |
refactor |
Code restructure (no behavior change) | refactor(services): extract validation logic |
docs |
Documentation only | docs(readme): update setup instructions |
test |
Adding/updating tests | test(users): add integration tests for CRUD |
chore |
Build, deps, config | chore(deps): update dependencies |
style |
Formatting only | style(api): fix indentation |
ci |
CI/CD changes | ci(actions): add staging deploy workflow |
Scope Examples
Use your project's module names:
auth, users, api, database, frontend, tests, docker, deploy, config, docs
When to Remind About Git
| Scenario | Action |
|---|---|
| New feature implemented | Suggest feat: commit |
| Bug fixed | Suggest fix: commit |
| Tests added | Suggest test: commit |
| Docs updated | Suggest docs: commit |
| 3+ files modified | Remind to commit |
| Starting new work | Remind to pull first |
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 · 74 lines · 497 tokens per session scan A e0aace78ec28
plan-forge git-workflow.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 21d ago), licensed MIT. It adds 497 tokens to every session, about $0.0025 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 instructions, from other repositories
dotnet-skills AGENTS.md
Instructions for managedcode/dotnet-skills, covering agents.md, purpose, solution topology, rule precedence and path and linking rules.
dotnet-skills copilot-instructions.md
Instructions for managedcode/dotnet-skills: Use AGENTS.md as the repository-wide source of truth for workflow, catalog structure, release policy, and skill maintenance rules.
Perigon.CLI copilot-instructions.md
Instructions for AterDev/Perigon.CLI, covering github copilot instructions, general guidelines, 技术栈, 项目结构与分层 and 代码风格约定.
copilot-instructions copilot-instructions.md
Instructions for SebastienDegodez/copilot-instructions, covering copilot instructions, language policy, development code generation and workflow implementation.
maf-doctor maf-deployment.instructions.md
Always-loaded production-deployment patterns for MAF 1.3.0. Auto-applies to Program.cs, DI registration files, and infra config. Covers ManagedIdentityCredential, MaxTokens caps, secret handling, OpenTelemetry wiring, and the analyzer rules that catch regressions at write time.
maf-doctor copilot-instructions.md
Instructions for joslat/maf-doctor, covering maf 1.3.0 migration — auto-loaded constraints, maf 1.3.0 — constraints & breaking changes reference, hard constraints (never violate), fan-out / fan-in rules (silent failure risk) and key breaking changes.