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/leonnonnast/mcpdevprompts/claude-mdgit clone --depth 1 https://github.com/LeonNonnast/mcpdevpromptsWrote 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/leonnonnast/mcpdevprompts/claude-md)<a href="https://agentmods.dev/instructions/leonnonnast/mcpdevprompts/claude-md"><img src="https://agentmods.dev/badge/instructions/leonnonnast/mcpdevprompts/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.1 | $0.00481 | $0.00481 |
| Opus 5 | $0.00241 | $0.00241 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
mcpdevprompts 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 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This repository contains the development workspace for an MCP (Modular Command Provider) server concept designed to serve curated prompts for AI development tools. The main idea is documented in docs/idea.md and involves creating a lightweight service that returns proven prompts for various development tasks.
Claude Code Configuration
The repository uses Claude Code's profile system with a specialized "Ideen-Analystin" (Ideas Analyst) role:
Custom Profile: Mira (Product Strategy Analyst)
- Profile File:
.claude/profiles/ia-profile.md - Onboarding Command:
/ia-onboarding(defined in.claude/commands/ia-onboarding.md) - Purpose: Systematically analyzes creative product ideas with unconventional thinking
- Analysis Format: Structured analysis including problem space exploration, solution strengthening, and strategic questions
Key Profile Behaviors
- Explores problem spaces beyond surface assumptions
- Strengthens ideas through "steelmanning" approach
- Provides concrete improvement suggestions
- Generates 3-5 strategic questions for further development
- Focuses on user needs, market logic, and systemic thinking
Repository Structure
mcpdevprompts/
├── .claude/
│ ├── commands/ia-onboarding.md # Custom slash command for IA onboarding
│ ├── profiles/ia-profile.md # Complete IA profile definition
│ └── settings.local.json # Local permissions and settings
├── docs/
│ └── idea.md # Core project concept documentation
└── CLAUDE.md # This file
Expected Input Format for Ideas Analysis
When using the IA profile, provide ideas in this format:
# Pitch Name
## Problem
[Problem description]
## Lösung
[Solution description]
## Rabbit Holes
[Potential complexities or side considerations]
Development Context
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 · 64 lines · 481 tokens per session scan A 4a9833efa5be
mcpdevprompts CLAUDE.md is an instructions file published in the GitHub repository LeonNonnast/mcpdevprompts (1 stars, last pushed 1y ago), licensed MIT. It adds 481 tokens to every session, about $0.0024 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
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).