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 skills add drhalto/agentmako --skill mako-code-intelgit 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-code-intel)<a href="https://agentmods.dev/skills/drhalto/agentmako/mako-code-intel"><img src="https://agentmods.dev/badge/skills/drhalto/agentmako/mako-code-intel/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/drhalto/agentmako/mako-code-intel"><img src="https://agentmods.dev/badge/skills/drhalto/agentmako/mako-code-intel.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.00961 |
| Opus 5.5 | $0.00020 | $0.00384 |
| Sonnet 5.5 | $0.00010 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
mako-code-intel 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mako Code Intel
Use this skill for static code queries that are best answered by syntax-aware
search or diagnostics. It is not the general repo-orientation skill; use
repo_map through /mako-ai:mako-discovery for that.
Tools
ast_find_pattern
Use for structural code pattern search over indexed TypeScript, TSX, JavaScript, and JSX files.
- Best for finding syntax shapes that text search may miss.
- Use for patterns such as function calls, JSX attributes, hook usage, imports, conditionals, or unsafe constructs.
- Keep searches bounded with focused patterns and file scopes when possible.
- TSX/JSX snippets starting with
{,[, or<also run with parser context, so callers usually do not need to wrap lone object or JSX patterns. CheckpatternAttemptsand matchpatternVariantwhen you need to know whether the original or auto-anchored form matched. - List metavariables in
captureswhen you need captured values returned. - If the result is a false positive that should not recur, use
finding_ackfrom/mako-ai:mako-workflowwith the returnedackableFingerprint.
lint_files
Use for focused lint/static diagnostics against selected files.
- Best after editing files or when reviewing a known suspect area.
- Defaults to compact output; pass
verbosity: "full"ormaxFindingswhen broad diagnostics are actually needed. - YAML rule packs under
.mako/ruleshot-reload in long-running MCP sessions. - For helper-bypass checks, rule packs may declare
canonicalHelperwith a helpersymboland optionalpath; matching files that already reference the helper are suppressed, while bypasses emit producer/consumer context. - Use the returned finding identity/fingerprint when acknowledging reviewed diagnostics.
- Do not use
agent_feedbackto suppress a diagnostic; usefinding_ack.
extract_rule_template
Use after a fix lands and the removed shape should become future project knowledge.
- Pass the local git
fixCommit; optionally passbaseCommit,filePath, andruleIdPrefix. - Treat the returned
draftYamlas a draft. Review broad patterns and caveats before placing it under.mako/rules. - Follow with
rule_pack_validateand a focusedlint_filesrun before relying on the new 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.
- 1mo ago First seen · 93 lines · 50 tokens per session scan A 71c4b44c0e59
mako-code-intel is a skill published in the GitHub repository drhalto/agentmako (54 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 961 once invoked, about $0.0002 per session on Opus 5.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.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
diagnosing-superpowers
A diagnostic workflow for investigating problems in Superpowers agent sessions using saved conversation records. It requires evidence linked to exact file paths and line numbers, then organizes findings into a report.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.