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.
git clone --depth 1 https://github.com/Clear-Sights/MakotoWrote 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/plugins/clear-sights/makoto/plugin)<a href="https://agentmods.dev/plugins/clear-sights/makoto/plugin"><img src="https://agentmods.dev/badge/plugins/clear-sights/makoto/plugin/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/plugins/clear-sights/makoto/plugin"><img src="https://agentmods.dev/badge/plugins/clear-sights/makoto/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
makoto 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 6d 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.
What it actually says
{
"name": "makoto",
"description": "Form-based session record holds before writes, commit/push and final answers.",
"version": "5.0.8",
"author": {
"name": "Clear-Sights"
},
"homepage": "https://github.com/Clear-Sights/Makoto",
"repository": "https://github.com/Clear-Sights/Makoto",
"license": "Apache-2.0",
"keywords": [
"claude-code",
"guardrails",
"integrity",
"hooks",
"makoto"
]
}
What it installs
The manifest is a name and a version. 6 hooks travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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.
- 6d ago Changed 85bde8c88faa
- 7d ago Changed b3ec40702493
- 9d ago Changed 02ddbbe9f524
- 10d ago Changed bd3de70e2d11
- 11d ago Changed 150e53e59c4d
- 13d ago Changed 0486ee30d970
- 14d ago Changed · +8 lines 59affe1e1d20
- 16d ago Changed d8a24bff27dd
- 17d ago Changed 3667a0656505
- 18d ago First seen · 11 lines scan A 46f5e4c4a2fa
makoto is a plugin published in the GitHub repository Clear-Sights/Makoto (45 stars, last pushed 4d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
agentlint
Claude Code marketplace wrapper for AgentLint's AI-agent guardrail engine. 77 rules across 8 packs, hybrid AgentChute security feeds, circuit-breaker visibility, inline-ignore reasons.
hush
Quieter sessions for Claude Code: less narration, shorter tool output and concise answers focused on the result.
fable-baton
Turns Fable 5 into a token-frugal orchestrator: Fable keeps judgment, tiered Opus/Sonnet/Haiku agents do the labor.
ballast
Builds up to a goal in a field you have no expertise in: splits it into the foundations that goal actually needs, mobilizes what you already hold, learns what is missing, and leaves every solved path behind for the next goal. Nothing is called done until a check passes.
razor
Reuse-first checks for Claude Code: reconsider dependencies, file growth and unnecessary code before adding more.
handoff
Portable project memory + development workflow for coding agents: auto-loads STATUS+RULES each session, enforces folder-level CONTEXT.md on edit, nudges durable state updates at turn end, scaffolds the system into any repo via guided discovery, and ships a tiered 6-phase workflow skill set covering every phase (brief.