Skill-Madness: Instructions file for Codex

AGENTS.md

Skill-Madness AGENTS.md is an instructions file for Codex, OpenCode from ivy00johns/Skill-Madness. It costs 505 tokens per session, scanned A, original, MIT.

Repository instructions for contributors and coding agents working on the Skill-Madness project. They explain where skill-development workspaces belong, which files to consult, and how to check Markdown files.

In plain words
What is it for?
Use them when creating or updating skills, working in the repository, choosing workspace locations, checking project documentation, or running Markdown lint checks.
Why use it?
They prevent common project-maintenance mistakes, such as putting temporary work in the wrong directory or leaving documentation with lint errors. They also clarify which instructions take priority.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions AGENTS.md; mentions Codex.

This is ivy00johns/Skill-Madness's own configuration. It tells Codex and OpenCode how to work on Skill-Madness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Skill-Madness configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ivy00johns/Skill-Madness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ivy00johns/Skill-Madness/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ivy00johns/Skill-Madness

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for Skill-Madness AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ivy00johns/skill-madness/agents-md/github.svg)](https://agentmods.dev/instructions/ivy00johns/skill-madness/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ivy00johns/skill-madness/agents-md"><img src="https://agentmods.dev/badge/instructions/ivy00johns/skill-madness/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.

agentmods 80×15 button for Skill-Madness AGENTS.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 505 This file is loaded in full into every session.
When invoked 505 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00505 $0.00505
Opus 5.5 $0.00202 $0.00202
Sonnet 5.5 $0.00101 $0.00101
Haiku 4.5 $0.00051 $0.00051

Measured 2mo ago against content hash e19ccc0c1b95, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

AGENTS.md · 53 lines

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:

  1. Add the variable (with empty value and a comment) to .env.example
  2. Have the skill's scripts read from the repo root .env
  3. Document which skill uses it in the .env.example section 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"

Read the full file on GitHub · 53 lines

Changes

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.

  1. 2mo ago First seen · 53 lines · 505 tokens per session scan A e19ccc0c1b95

Subscribe to this mod's changes

Skill-Madness AGENTS.md is an instructions file published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 4d ago), licensed MIT. It adds 505 tokens to every session, about $0.0020 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,750 tokens

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.

denoland/deno · 3,077 tokens