Borrowing it
Nothing to install: this file belongs to srnichols/plan-forge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/srnichols/plan-forge/master/.github/instructions/git-workflow.instructions.mdgit 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/instructions/srnichols/plan-forge/git-workflow)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/git-workflow"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/git-workflow/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/instructions/srnichols/plan-forge/git-workflow"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/git-workflow.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.00497 | $0.00497 |
| Opus 5.5 | $0.00199 | $0.00199 |
| Sonnet 5.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 1mo 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.
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.
- 1mo ago 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 (6 stars, last pushed today), licensed MIT. It adds 497 tokens to every session, about $0.0020 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).