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/ivy00johns/skill-madness/agents-mdgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/agents-md)<a href="https://agentmods.dev/instructions/ivy00johns/skill-madness/agents-md"><img src="https://agentmods.dev/badge/instructions/ivy00johns/skill-madness/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.1 | $0.00505 | $0.00505 |
| Opus 5 | $0.00253 | $0.00253 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
Skill-Madness 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Shared instructions for all AI coding agents (Claude Code, Gemini CLI, Codex, etc.) working in this repo.
Skill Creator Workspaces
When using /skill-creator (or any skill evaluation workflow) to audit, test, or iterate on skills, always place workspace directories in .workspaces/ at the repo root — not as siblings to the skill directory. This overrides skill-creator's default behavior of creating <skill-name>-workspace/ next to the skill.
# Use this:
.workspaces/<skill-name>/iteration-1/...
# NOT this:
skills/workflows/<skill-name>-workspace/...
# or:
<skill-name>-workspace/...
Both .workspaces/ and *-workspace/ are gitignored, but consolidating into .workspaces/ keeps the repo clean and avoids stray directories.
Markdownlint
This repo has a .markdownlint.json config at the root. When creating or editing any Markdown
file — especially SKILL.md files via skill-creator — always fix markdownlint violations before
finishing. Run a lint pass on every Markdown file you touch and resolve all warnings. The repo
disables MD013 (line length) and MD060 globally; all other rules are enforced.
Environment Variables for Skills
All API keys and credentials for skills live in a single root .env file at the repo root — never in per-skill .env files. This keeps secrets centralized and avoids confusion as the skill count grows.
.env— The live credentials file (gitignored, never committed).env.example— Template documenting every variable across all skills (committed, no real values)
When a skill needs a new env var:
- Add the variable (with empty value and a comment) to
.env.example - Have the skill's scripts read from the repo root
.env - Document which skill uses it in the
.env.examplesection header
Scripts should walk up from their location to find the repo root .env. Pattern:
import pathlib, os
_repo_root = pathlib.Path(__file__).resolve().parent
while _repo_root != _repo_root.parent:
if (_repo_root / ".env.example").exists():
break
_repo_root = _repo_root.parent
# Then load _repo_root / ".env"
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.
- 5d ago First seen · 53 lines · 505 tokens per session scan A e19ccc0c1b95
Skill-Madness AGENTS.md is an instructions file published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 25d ago), licensed MIT. It adds 505 tokens to every session, about $0.0025 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-30.
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.
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.
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.
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).