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/humzakt/dev-starter-kit/agents-mdgit clone --depth 1 https://github.com/humzakt/dev-starter-kitWhat 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.00936 | $0.00936 |
| Opus 5 | $0.00468 | $0.00468 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
dev-starter-kit 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 2d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Project Instructions for AI Coding Agents
This file is automatically read by AI coding tools (Codex, Cursor, Claude Code, Copilot, Windsurf, etc.) to understand project conventions and act as a senior engineer.
Project Overview
This is a Python project. All source code lives in src/, tests in tests/, and documentation in docs/.
Build & Run
# Setup
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
pip install -e ".[dev]"
# Lint
ruff check . && ruff format --check .
# Fix lint issues
ruff check --fix . && ruff format .
# Run tests
pytest tests/ -v
# Pre-commit hooks
pre-commit install
pre-commit run --all-files
Code Style & Conventions
- Python 3.11+ required
- Ruff for linting and formatting (configured in
pyproject.toml) - Line length: 120 characters
- Quote style: double quotes
- Imports: sorted by isort (via Ruff)
- Type hints: use them on all public functions and method signatures
- Docstrings: use Google-style docstrings for public functions and classes
- No bare
except:— always catch specific exceptions - Prefer
pathlib.Pathoveros.path - Use f-strings over
.format()or%
Testing
- Test files go in
tests/with naming patterntest_<module_name>.py - Test classes:
Test<ModuleName> - Test methods:
test_<function_name>[_<scenario>] - Use
pytestfixtures for setup/teardown - Mock external dependencies (APIs, databases) — never make real network calls in tests
- Every PR that changes source files must include corresponding tests (enforced by CI)
Git & PR Workflow
- Branch from
main - Branch naming:
feat/description,fix/description,chore/description - Commit messages follow Conventional Commits:
feat:new featurefix:bug fixchore:maintenancedocs:documentationstyle:formatting (no logic change)refactor:code restructure (no behavior change)test:adding/updating tests
- PRs require passing CI checks before merge
- Squash merge to
main
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.
- 2d ago First seen · 112 lines · 936 tokens per session scan A 324f1c08c5f6
dev-starter-kit AGENTS.md is an instructions file published in the GitHub repository humzakt/dev-starter-kit (3 stars, last pushed 6mo ago), licensed MIT. It adds 936 tokens to every session, about $0.0047 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.