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/sflandergan/agentic-coding/agents-mdgit clone --depth 1 https://github.com/sflandergan/agentic-codingWhat 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.00909 | $0.00909 |
| Opus 5 | $0.00454 | $0.00454 |
| Sonnet 5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
agentic-coding 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 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Shared conventions for AI agents maintaining this toolkit repo. This file is loaded every session.
What This Repo Is
A reusable agentic coding toolkit. The core/ and stacks/ trees are templates installed into other repos by scripts/init.sh and scripts/copy.sh. There is no application code, no DDD contexts, and no test suite — only markdown templates and bash scripts.
Maintenance Surface
The files this repo's agents operate on:
- Markdown templates under
core/andstacks/ README.mdskills-lock.jsonfor this repo's self-maintenance skillscore/skills-lock.jsonfor the toolkit installed into target reposscripts/init.sh(~325 lines),scripts/copy.sh(~618 lines)
Dot-Mapping (Source → Target)
The scripts copy these source directories to target dot-directories:
| Source in repo | Target dot-directory |
|---|---|
core/opencode/ |
.opencode/ |
core/claude/ |
.claude/ |
core/agents/ |
.agents/ |
core/docs/ |
docs/ |
Core + Stacks Dual-Maintenance
When modifying a file under core/, check whether stacks/pnpm/ or stacks/maven/ has an overlay for the same file. Update stack overlays when the change affects stack-specific installed output, especially when adding a new template or changing behavior that an overlay intentionally customizes.
Sync Invariants
These must stay consistent with the actual files:
README.mdagent/skill lists- The dot-mapping table above
- Agent file names in
.opencode/agents/vs whatopencode.jsonreferences
Skill Lockfile Scopes
The two lockfiles have different scopes and are not expected to match.
skills-lock.jsontracks remote skills installed in this repo for self-maintenance. Compare it against remote-sourced skill directories under.agents/skills/.core/skills-lock.jsontracks remote skills installed into target repos byscripts/init.shandscripts/copy.sh. Compare it against the skills the toolkit templates install for downstream projects.
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 · 87 lines · 909 tokens per session scan A 2e7652f58833
agentic-coding AGENTS.md is an instructions file published in the GitHub repository sflandergan/agentic-coding (2 stars, last pushed 2mo ago), licensed MIT. It adds 909 tokens to every session, about $0.0045 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.