Borrowing it
Nothing to install: this file belongs to bodangren/git-workflow. 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/bodangren/git-workflow/main/AGENTS.mdgit clone --depth 1 https://github.com/bodangren/git-workflowWrote 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/bodangren/git-workflow/agents-md)<a href="https://agentmods.dev/instructions/bodangren/git-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/bodangren/git-workflow/agents-md/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/bodangren/git-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/bodangren/git-workflow/agents-md.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.00761 | $0.00761 |
| Opus 5.5 | $0.00304 | $0.00304 |
| Sonnet 5.5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
git-workflow AGENTS.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 2mo 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenticDev Agent Guide
This project uses AgenticDev, a modular, spec-driven development methodology. The workflow is broken down into several discrete skills located in the skills/ and .claude/skills/ directories.
Core Philosophy
- Specs as Code: All specification changes are proposed and approved via Pull Requests.
- Just-in-Time Context: Use the
doc-indexerskill to get a real-time map of all project documentation. - Sprint-Based: Work is organized into GitHub Milestones and planned via the
sprint-plannerskill. - Atomic Issues: Implementation is done via atomic GitHub Issues, which are executed by the
issue-executorskill. - Hybrid Architecture: LLM executes workflow steps with strategic reasoning, helper scripts automate repetitive tasks.
Available Skillsets
Each skill contains comprehensive documentation in SKILL.md (50-262 lines) explaining purpose, workflow, and error handling. Helper scripts are located in each skill's scripts/ directory.
skills/skill-lister/: For listing all available skills and their descriptions.skills/project-init/: Initialize AgenticDev directory structure in new projects. Creates docs/specs and docs/changes directories.skills/project-migrate/: Migrate existing (brownfield) projects with established documentation to AgenticDev structure. Intelligently discovers, categorizes, and migrates documentation while preserving content, adding frontmatter, and maintaining git history.skills/prd-authoring/: Guide early-stage project planning through Product Requirements Documents (PRDs). Manages the complete workflow from initial product briefs through market research, PRD creation, validation, and epic decomposition. Bridges the gap between project ideas and spec-driven development with data-driven requirements and measurable success criteria.skills/doc-indexer/: Scan and index project documentation for just-in-time context discovery. Provides a map of all available docs without loading full content.skills/spec-authoring/: Create and refine specification proposals via Spec PR workflow. Supports both proposing new specs and updating based on review feedback.skills/sprint-planner/: Plan sprints by creating GitHub milestones and issues from approved specs. Automates issue creation while LLM guides strategic planning.skills/issue-executor/: Execute development workflow for a single issue. Loads full context (specs, retrospective, doc index) and creates feature branch.skills/change-integrator/: Integrate completed changes post-merge. Moves specs to source-of-truth, updates retrospective, and cleans up branches.skills/doc-validator/: Validate that Markdown files are in standard locations. Scans for .md files outside of predefined allowed directories and outputs warnings to prevent documentation sprawl.skills/agent-integrator/: Create or update this AGENTS.md file. Uses marker-based idempotent updates to register AgenticDev capabilities.
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.
- 2mo ago First seen · 39 lines · 761 tokens per session scan A d9b3c4e5570e
git-workflow AGENTS.md is an instructions file published in the GitHub repository bodangren/git-workflow (11 stars, last pushed 10mo ago), licensed MIT. It adds 761 tokens to every session, about $0.0030 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-30.
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.