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/megamen32/gptadmin_opensource/claude-mdgit clone --depth 1 https://github.com/megamen32/gptadmin_opensourceWrote 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/megamen32/gptadmin_opensource/claude-md)<a href="https://agentmods.dev/instructions/megamen32/gptadmin_opensource/claude-md"><img src="https://agentmods.dev/badge/instructions/megamen32/gptadmin_opensource/claude-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 | $0.01062 | $0.01062 |
| Opus 5 | $0.00531 | $0.00531 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
gptadmin_opensource CLAUDE.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 3d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago First seen · 85 lines · 1,062 tokens per session scan A 40b538697e11
gptadmin_opensource CLAUDE.md is an instructions file published in the GitHub repository megamen32/gptadmin_opensource (10 stars, last pushed 25d ago), licensed AGPL-3.0. It adds 1,062 tokens to every session, about $0.0053 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
ebay-mcp AGENTS.md
Instructions for YosefHayim/ebay-mcp, covering agents.md, what this is, instruction sources, validation commands and module map (src/).
mcp-odoo CLAUDE.md
Claude Code instructions for erpipe-org/mcp-odoo: Guidance for Claude Code (claude.ai/code) working in this repository.
ebay-mcp copilot-instructions.md
Instructions for YosefHayim/ebay-mcp, covering github copilot instructions, core expectations, schema and api patterns, documentation and tests and validation.
link CLAUDE.md
Instructions for lanes-sh/link, covering working in this repository, work on a branch, in a worktree, never run lanes link from a worktree without laneslinkhome, anything touching a real account is the operator's call and a release publishes, and npm does not give a version back.
ebay-mcp CLAUDE.md
Instructions for YosefHayim/ebay-mcp, covering claude.md and claude-specific notes.
teamxray copilot-instructions.md
Instructions for AndreaGriffiths11/teamxray, covering github copilot instructions for mcp team x-ray extension, response style, build, test, and lint commands, validating extension changes and architecture.