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-workflownpx skills add drhalto/agentmako --skill mako-workflowgit 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-workflow)<a href="https://agentmods.dev/skills/drhalto/agentmako/mako-workflow"><img src="https://agentmods.dev/badge/skills/drhalto/agentmako/mako-workflow.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.00107 | $0.00977 |
| Opus 5 | $0.00053 | $0.00489 |
| Sonnet 5 | $0.00021 | $0.00195 |
| Haiku 4.5 | $0.00011 | $0.00098 |
Grade A, and why
mako-workflow 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mako Workflow
Use this skill when the user needs a workflow output rather than a single trace: investigation packets, pre-implementation or review artifacts, prior-session recall, feedback, telemetry, or finding acknowledgements.
Operator And Workflow Tools
suggest
Use to propose useful Mako queries or investigation directions.
investigate
Use to run a broader bounded investigation workflow around a target.
workflow_packet
Use to produce a bundled workflow summary from gathered context.
tenant_leak_audit
Use to inspect likely tenant-boundary and data-leak risks.
- Pair with
db_rls,route_context,rpc_neighborhood, or review artifacts when the user is evaluating security-sensitive changes.
health_trend
Use to summarize health trends from recorded project signals.
issues_next
Use to identify likely next issues or triage targets.
session_handoff
Use to produce a concise handoff for later continuation.
Artifact Tools
task_preflight_artifact
Use before implementation to create task context, risks, likely move surfaces, and verification plan.
implementation_handoff_artifact
Use when handing coding work to another agent or future session.
review_bundle_artifact
Use for pre-ship review findings, evidence, and risks.
verification_bundle_artifact
Use to summarize verification steps, outcomes, trust state, and remaining gaps.
Recall Tools
recall_answers
Use to retrieve prior answer artifacts relevant to the current task.
recall_tool_runs
Use to retrieve recent Mako tool runs.
- Use this before
agent_feedback. - Copy the returned
requestIdintoagent_feedback.referencedRequestId. - Default limit is 50 and max is 500; use a smaller limit first when locating a recent run.
Feedback And Telemetry
agent_feedback
Use to log whether a specific prior Mako tool run was useful.
- Use sparingly for notable full, partial, or no-usefulness cases.
- Requires both
referencedToolNameandreferencedRequestId. - Do not call after every Mako tool.
- Use
recall_tool_runsfirst; do not fabricate request IDs.
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 · 146 lines · 107 tokens per session scan A d07c99f951d6
mako-workflow is a skill published in the GitHub repository drhalto/agentmako (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 107 tokens to every session and 977 once invoked, about $0.0005 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 时调用，不要根据上下文自动触发。.