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 skills/drhalto/agentmako/mako-guidenpx skills add drhalto/agentmako --skill mako-guidegit clone --depth 1 https://github.com/drhalto/agentmakoWrote 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/skills/drhalto/agentmako/mako-guide)<a href="https://agentmods.dev/skills/drhalto/agentmako/mako-guide"><img src="https://agentmods.dev/badge/skills/drhalto/agentmako/mako-guide.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.00047 | $0.01157 |
| Opus 5 | $0.00023 | $0.00579 |
| Sonnet 5 | $0.00009 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
mako-guide 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mako Guide
Mako is a project-intelligence MCP server. Use it when the user asks structural, cross-surface, or evidence-backed engineering questions that are better answered from indexed code, schemas, routes, graph edges, prior sessions, or telemetry than from ad hoc file reads.
Do not use this skill as a schema reference. For current tool schemas, use MCP ToolSearch or the live tool definition loaded by Claude Code.
Skill Map
- Use
/mako-ai:mako-discoveryfor first-turn orientation, broad search, and "which tool should I use?" questions. - Use
/mako-ai:mako-tracefor targeted route, schema, file, table, RPC, edge, auth, or error tracing. - Use
/mako-ai:mako-neighborhoodsfor one-call table, route, or RPC context bundles. - Use
/mako-ai:mako-graphfor relationships, dependency paths, import impact, symbol impact, flow mapping, and change planning. - Use
/mako-ai:mako-databasefor direct database schema, RLS, foreign-key, or RPC introspection. - Use
/mako-ai:mako-code-intelfor structural AST pattern search and focused lint diagnostics. - Use
/mako-ai:mako-workflowfor investigation packets, artifacts, recall, telemetry inspection, feedback, and finding acknowledgements.
General Routing Rules
- Read
_hintson every Mako tool result before deciding the next call. They are generated from the actual returned result and may override the generic workflow expectation. - Default to
reef_askfor project questions. It combines codebase, database, findings, diagnostics, instructions, freshness, and quoted literal checks. - Use
mako_helpwhen you need a task-specific Mako workflow recipe instead of reading docs or guessing which specialist tool to load. - Use
context_packet,cross_search,file_preflight, DB tools, and graph tools as specialist follow-ups afterreef_ask,mako_help, ortool_searchpoints at a concrete need. - Prefer Mako over built-in grep when the question is about relationships, not literal text.
- Built-in text search is fine for exact strings inside known files.
- Start broad only when the target is unknown; switch to targeted tools once you have a route, table, RPC, file, or symbol.
- Do not invent schemas, arguments, request IDs, finding fingerprints, or telemetry events.
- If a tool name is uncertain, use
tool_searchbefore calling a Mako tool.
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 · 114 lines · 47 tokens per session scan A a1f0295a00eb
mako-guide is a skill published in the GitHub repository drhalto/agentmako (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,157 once invoked, about $0.0002 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-30.
Other skills, from other repositories
ctxo-safe-edit
Use BEFORE editing, renaming, or deleting any function, class, or method, to avoid breaking dependents.
ctxo-understand
Use at the START of any code task (fix, extend, refactor, understand) before reading source files, to orient with ctxo and avoid going in the wrong direction.
ctxo-review-pr
Use when reviewing a PR, a diff, or recent changes, to get a full risk assessment in one call.
composer-prompting
Internal guidance for shaping a well-specified coding task into a tight Cursor/Composer prompt before delegating it via /cursor:delegate.
figma-design-system-to-design-md
Figma design system to design.md — Extract Figma design system into a structured design.md. Use when user says 'generate design.md', 'extract design system', 'design tokens to markdown', 'create design doc from Figma', 'Figma design system to design.md', or wants to document their design system from token files and…
chinese-documentation
中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发。.