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/natea/makerperks/claude-mdgit clone --depth 1 https://github.com/natea/makerperksWrote 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/natea/makerperks/claude-md)<a href="https://agentmods.dev/instructions/natea/makerperks/claude-md"><img src="https://agentmods.dev/badge/instructions/natea/makerperks/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.01113 | $0.01113 |
| Opus 5 | $0.00557 | $0.00557 |
| Sonnet 5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
makerperks 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 4d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MakerPerks
A browseable, agent-friendly directory of builder perks (free credits, discounts, and programs) for startups, students, OSS maintainers, indie devs, and non-profits.
- Domains:
makerperks.com(site) ·makerperks.dev(agent endpoints / redirect) - Spec workflow: OpenSpec (see below). Active changes live in
openspec/changes/; runopenspec listto see them. - Stack: Astro · content collections (one YAML file per program) · JSON-Schema validated · static, PR-editable, no backend.
Design Context
Strategic product context lives in PRODUCT.md (register, users, personality,
anti-references, design principles, a11y). The visual system lives in DESIGN.md
("The Trusted Ledger" — tokens are resolved in src/styles/global.css). Read
PRODUCT.md before any UI work.
Quick reference:
- Register: product (design serves fast browse/filter/scan + trust)
- Personality: trustworthy & precise — dependable, clear, current
- Anti-references: SaaS-cream AI slop · plain markdown awesome-list · cluttered coupon/deals site · stiff corporate enterprise
- Accessibility: WCAG 2.2 AA
Design workflow — use Impeccable for ALL design work
Any change that touches the site's look, layout, or UX MUST go through the
impeccable skill (impeccable:impeccable plugin), not ad-hoc CSS/markup edits.
This applies to: pages, components, layout, spacing, typography, color, motion,
responsive behavior, empty/error states, UX copy, and accessibility passes.
- New surface:
/impeccable craft <feature>(shape → build end-to-end). - Plan first:
/impeccable shape <feature>. - Improve existing:
/impeccable critique|audit|polish|layout|colorize|typeset| animate|clarify <target>. - Seed/refresh the visual system:
/impeccable document→ writesDESIGN.md. - Iterate in-browser:
/impeccable live.
Impeccable reads PRODUCT.md (and DESIGN.md) first and enforces the anti-references above. Do not hand-roll UI that bypasses it — on-brand, slop-free output is the whole point. Backend/data/ingest work (YAML records, schema, build scripts, agent outputs) does not require impeccable; it is for the frontend/design surface.
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.
- 4d ago First seen · 89 lines · 1,113 tokens per session scan A f20cc5c35f7a
makerperks CLAUDE.md is an instructions file published in the GitHub repository natea/makerperks (5 stars, last pushed 4d ago), licensed MIT. It adds 1,113 tokens to every session, about $0.0056 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.