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 skills add nimble-giant/nimble-mold --skill init-agents-mdgit clone --depth 1 https://github.com/nimble-giant/nimble-moldWrote 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/skills/nimble-giant/nimble-mold/init-agents-md)<a href="https://agentmods.dev/skills/nimble-giant/nimble-mold/init-agents-md"><img src="https://agentmods.dev/badge/skills/nimble-giant/nimble-mold/init-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.
<a href="https://agentmods.dev/skills/nimble-giant/nimble-mold/init-agents-md"><img src="https://agentmods.dev/badge/skills/nimble-giant/nimble-mold/init-agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.01299 |
| Opus 5 | $0.00022 | $0.00649 |
| Sonnet 5 | $0.00009 | $0.00260 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
init-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 9d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init AGENTS.md
Purpose
This command researches the current project and generates a holistic AGENTS.md file following AGENTS.md best practices. If a CLAUDE.md file exists, it is used as a source for content. The result is a portable, agent-agnostic instruction file that works across AI coding agents.
Command Name
init-agents-md
Invocation Syntax
/init-agents-md
Workflow
When this command is invoked:
Phase 1: Research the Project
Thoroughly explore the project to understand its structure, conventions, and tooling:
- Project overview — Read
README.md,package.json,Cargo.toml,go.mod,pyproject.toml, or equivalent to identify the tech stack, language(s), frameworks, and purpose - Build & test commands — Identify how to install dependencies, build, lint, and run tests
- Code style — Look for linter configs (
.eslintrc,.prettierrc,rustfmt.toml, etc.), formatting rules, and naming conventions - Project structure — Map key directories and their roles
- Git conventions — Check for
.commitlintrc, commit history patterns, branch naming conventions - Existing AI instructions — Read
CLAUDE.md,.cursorrules,.github/copilot-instructions.md, or any existing agent config files - CI/CD — Check
.github/workflows/,Makefile,Dockerfile, or deployment configs - Boundaries — Identify sensitive files, directories, or patterns that agents should not modify (e.g.,
.env, generated files, vendor directories)
Phase 2: Draft the AGENTS.md
Generate an AGENTS.md file following these guidelines:
Target length: Under 150 lines. If the project needs more coverage, use progressive disclosure — link to separate .md files for detailed topics.
Required sections (adapt headings to fit the project):
# AGENTS.md
## Project Overview
[1-3 sentences: what this project is, tech stack with versions, primary language]
## Setup
[Exact commands to install, build, and run]
## Testing
[How to run tests, test conventions, CI expectations]
## Code Style
[Formatting rules, naming conventions, key patterns — use examples over descriptions]
## Project Structure
[Key directories and their roles — keep it scannable]
## Git Conventions
[Commit format, branch naming, PR expectations]
## Boundaries
[What agents should NOT modify, sensitive areas, generated files]
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.
- 9d ago First seen · 116 lines · 44 tokens per session scan A 081e30816813
init-agents-md is a skill published in the GitHub repository nimble-giant/nimble-mold (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,299 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…