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/sungurerdim/dev-skills/agents-mdgit clone --depth 1 https://github.com/sungurerdim/dev-skillsWrote 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/sungurerdim/dev-skills/agents-md)<a href="https://agentmods.dev/instructions/sungurerdim/dev-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/sungurerdim/dev-skills/agents-md.svg" alt="Measured on agentmods" 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 | $0.01043 | $0.01043 |
| Opus 5 | $0.00522 | $0.00522 |
| Sonnet 5 | $0.00209 | $0.00209 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
dev-skills 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 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for any coding agent working on this repository. CLAUDE.md holds the same
essentials plus a Claude-Code-specific blueprint profile; nothing here needs to be read twice.
dev-skills is a catalog of 30 Agent Skills — pure markdown, zero runtime dependencies. The
only executable code is install.sh (+ its install.cmd Windows launcher), scripts/*.sh,
evals/tasks/*/*.sh, and ds-brief/assets/verify-brief.py. Shared references live in core/
and are linked from skills as ../core/<file>.md; the installer ships core/ on every install.
Commands
| Task | Command |
|---|---|
| Run the quality gate (do this before every commit) | bash scripts/quality.sh |
| Make the gate run on every commit | bash scripts/quality.sh --install-hook |
| Gate red | Fix what it names, re-run, then commit — the hook is never bypassed |
| Install the skills into a host | ./install.sh (or --target <dir>, --project <dir>, --skills a,b) |
| Install for a Claude-5 host with an always-on rules layer | ./install.sh --profile lean — strips the portable-only-marked blocks at install time; repo files always keep the full portable text |
| Install for Claude Code specifically | ./install.sh --profile claude — lean plus one Claude-only sentence injected into ds-ship's delegation step (delegates run as forked subagents); the repo file stays host-neutral |
| Check an installed copy for drift | ./install.sh --check (profile-aware — reads the profile from the version stamp) |
| See installed vs repo vs upstream at a glance | ./install.sh --status — read-only |
| Update an existing install | ./install.sh --update — git pull --ff-only + re-install with the stamped profile; never merges on your behalf |
The gate needs bash, python3, shellcheck, and typos. A missing tool fails the run loudly
and names what went unverified — never treat a skipped check as a passing one. There is no CI;
this gate is the only enforcement, by design.
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 Changed · +4 lines · +120 tokens per session a93e964585e5
- 3d ago First seen · 54 lines · 923 tokens per session scan A 8b5f17ce6a2a
dev-skills AGENTS.md is an instructions file published in the GitHub repository sungurerdim/dev-skills (1 stars, last pushed today), licensed MIT. It adds 1,043 tokens to every session, about $0.0052 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
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
agentic-tech-debt AGENTS.md
Instructions for bcanfield/agentic-tech-debt: The agent instructions for this repo live in CLAUDE.md — one source of truth for every coding agent. Read it and follow it as written; it applies to Codex exactly as it does to Claude Code.
zuvo CLAUDE.md
Claude Code instructions for greglas75/zuvo, covering zuvo plugin — project guide, what this repo is, tech stack, how to update after making changes and for yourself (dev testing, no marketplace push).