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/reiarseni/mockpost/claude-mdgit clone --depth 1 https://github.com/reiarseni/mockpostWrote 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/reiarseni/mockpost/claude-md)<a href="https://agentmods.dev/instructions/reiarseni/mockpost/claude-md"><img src="https://agentmods.dev/badge/instructions/reiarseni/mockpost/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.00963 | $0.00963 |
| Opus 5 | $0.00481 | $0.00481 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
mockpost 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — MockPost contribution workflow
This file documents the git workflow for MockPost: how commits, branches, issues and pull requests are named and structured. Every artifact must read as written by a senior developer — natural, concise, technical prose. No AI marks anywhere.
Language
All repository artifacts are in English: commit titles/bodies, branch names, issue titles/bodies, PR titles/bodies, code comments and docs. The only exception is communication in chat; everything committed is English.
Conventional commits
Format: <prefix>: <summary in third-person singular, max 72 chars>
Valid prefixes:
| Prefix | Use for |
|---|---|
feat |
New capability, improvement, refactor, infrastructure |
fix |
Bug correction or incorrect behavior |
chore |
Maintenance, dependencies, CI/CD, packaging, technical cleanup |
refactor |
Code restructuring without behavior change |
docs |
Documentation only |
test |
Tests only |
Rules:
- Summary in third-person singular ("adds X", "fixes Y") — never imperative ("add X").
- No accents, no parentheses, max 72 characters.
- Body — pick the case that applies, in order:
- A — No body: title fully explains the change.
- B — Short prose (small, unit-like change): 1-2 direct lines explaining the why or what for — not the what (that is the title/diff).
- C — Bulleted justifications (diverse commit): one
-line per area/reason.
- Body lines: max 72 chars.
- NEVER include
Co-Authored-Byor any AI attribution in any commit. - Footer: intermediate commits in a group use
Refs #N; the last commit of the group usesCloses #N(N = issue number).
Branches
Pattern: <prefix>/<N>-<kebab-case-description>
- Features, chores, spikes:
feat/12-verificacion-otp(see language note below). - Bug fixes:
fix/23-error-snapshot-nulo. - Description in kebab-case, lowercase, no accents.
Language note: commit titles and bodies are English, but branch descriptions stay in Spanish kebab-case by project convention. If you prefer English branches, say so once and it becomes the project rule.
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 · 95 lines · 963 tokens per session scan A b009b4392513
mockpost CLAUDE.md is an instructions file published in the GitHub repository reiarseni/mockpost (2 stars, last pushed 12d ago), licensed MIT. It adds 963 tokens to every session, about $0.0048 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
Vibelution AGENTS.md
AGENTS.md instructions for CCDawn/Vibelution, covering vibelution agent rules, 1. identity and priority, 2. global red lines, 3. start and routing and 3.0 每任务先 router.
RepoGuardian-RHD-Enterprise AGENTS.md
AGENTS.md instructions for romil569/RepoGuardian-RHD-Enterprise, covering repoguardian agent notes, architecture, local commands, data backends and safety rules.
Job-Agent commit.instructions.md
Instructions for Pukakiii/Job-Agent, covering commit message, guidelines and body.
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
dario CLAUDE.md
Claude Code instructions for askalf/dario, covering dario — notes for claude code (and other llm coding agents), commits and prs, style, scope and codex drift runner.
geolens CLAUDE.md
Claude Code instructions for geolens-io/geolens: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.