Borrowing it
Nothing to install: this file belongs to Nunley-Media-Group/nmg-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Nunley-Media-Group/nmg-plugins/main/AGENTS.mdgit clone --depth 1 https://github.com/Nunley-Media-Group/nmg-pluginsWrote 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/nunley-media-group/nmg-plugins/agents-md)<a href="https://agentmods.dev/instructions/nunley-media-group/nmg-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/nunley-media-group/nmg-plugins/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.00408 | $0.00408 |
| Opus 5 | $0.00204 | $0.00204 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
nmg-plugins 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 8d 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.
What it actually says
AGENTS.md
Project Overview
Plugin marketplace repository for Nunley Media Group. Each listed plugin lives in its own GitHub repository and is referenced from host-specific catalogs. No plugins are currently listed.
Repository Structure
.agents/plugins/marketplace.json — Codex marketplace index (Git-backed plugin entries)
.omp-plugin/marketplace.json — Preferred Oh My Pi marketplace catalog
.claude-plugin/marketplace.json — Claude-compatible index consumed by Pi and as OMP fallback
README.md — Public docs: how to add the marketplace, plugin pointers
Maintaining the Marketplace
When adding or removing a plugin:
- Edit
.agents/plugins/marketplace.json:- Add a new entry to the
pluginsarray, or remove an existing one - For a plugin repo whose
.codex-plugin/plugin.jsonlives at the repo root, use:{"source": {"source": "url", "url": "https://github.com/owner/name.git", "ref": "main"}} - If the plugin lives in a subdirectory, use
source: "git-subdir"with apath - Include
policy.installation,policy.authentication, andcategoryon every entry
- Add a new entry to the
- Keep the matching entries in
.omp-plugin/marketplace.jsonand.claude-plugin/marketplace.jsonsynchronized for Oh My Pi and Pi compatibility. - Run
node scripts/validate-marketplace.mjs. - Update
README.mdto list the plugin and its source repo. - Open a PR.
Version bumps happen entirely in each plugin's own repo; this marketplace file only changes when a plugin is added, removed, renamed, or repointed to a different ref or URL.
Plugin development (skills, agents, tests, releases) happens entirely in each plugin's own repo. This repo is intentionally thin — it only points users at the plugins that make up the marketplace.
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.
- 8d ago First seen · 34 lines · 408 tokens per session scan A 64634187aa17
nmg-plugins AGENTS.md is an instructions file published in the GitHub repository Nunley-Media-Group/nmg-plugins (2 stars, last pushed 18d ago), licensed MIT. It adds 408 tokens to every session, about $0.0020 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
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.
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).
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).
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.
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.