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/alicicek/tale-modeWrote 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/alicicek/tale-mode/tale-mode)<a href="https://agentmods.dev/plugins/alicicek/tale-mode/tale-mode"><img src="https://agentmods.dev/badge/plugins/alicicek/tale-mode/tale-mode/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/alicicek/tale-mode/tale-mode"><img src="https://agentmods.dev/badge/plugins/alicicek/tale-mode/tale-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tale-mode 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "tale-mode",
"displayName": "Tale Mode",
"version": "2.6.1",
"description": "A discipline mode for complex/high-stakes work: staged planning, decisions-with-receipts, verify-against-source, parallel delegation, adversarial review. Always-on core disciplines via a SessionStart hook, plus a self-armed autonomous loop (a deterministic Stop gate) that can also arm itself from a committed, content-hash-trusted .claude/tale-mode.json during a kickoff phase. Plan-mode investigation runs without a wall of permission dialogs: a fail-closed PreToolUse hook auto-approves provably read-only shell in plan mode only (kill switch TALE_PLAN_APPROVE=0; see SECURITY.md). Cross-platform: the skill + autonomous loop run on both Claude Code and OpenAI Codex (on Codex the loop needs the one-time `touch ~/.tale-mode-allow-cwd-root` opt-in \u2014 its hook subprocesses don't receive env config). Helper skills: trust (the two user-only opt-in files), seed-gates (suggest committed gates), end-phase (clear the phase marker). The optional read-only stuck-loop governor (one advisory model call per stuck goal) ships as the companion plugin tale-mode-governor.",
"author": {
"name": "Ali Cicek",
"url": "https://github.com/alicicek"
},
"homepage": "https://github.com/alicicek/tale-mode",
"repository": "https://github.com/alicicek/tale-mode",
"license": "MIT",
"keywords": [
"workflow",
"planning",
"discipline",
"stop-hook",
"autonomous-loop",
"review"
],
"defaultEnabled": true
}What it installs
The manifest is a name and a version. 6 skills, 2 commands, 1 agent travel with it, and installing the plugin installs all of them — 711 tokens a session between 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.
- 1mo ago First seen · 23 lines scan A 0d53152e0e93
tale-mode is a plugin published in the GitHub repository alicicek/tale-mode (37 stars, last pushed 3mo ago), licensed MIT. 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
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
dev-skills
Lightweight skills for users with existing workflows - coding best practices, testing principles, and design guidelines without recipe workflows or agents.
taxcraft
US tax and accounting work for people whose situation outgrew consumer software but who still do the prep themselves: multiple entities, K-1s that arrive late and wrong, basis and carryforwards nobody is tracking, quarterly estimates guessed at rather than computed. It builds the workpapers a CPA would build …
cpp-lsp
Claude Code plugin for C/C++ development with clangd LSP integration, 14 automated hooks for compilation, linting (clang-tidy), formatting (clang-format), and memory analysis (valgrind).
autonomous-dev marketplace
PROJECT.md-first autonomous development with 22 specialized agents, 28 skills, and 66 automation hooks. Full SDLC automation via /implement command. Zero scope creep with automatic PROJECT.md validation. Works for Python, JavaScript, TypeScript, and Go projects.
svelte-lsp
Svelte language server plugin for Claude Code with svelte-language-server integration and automated hooks for linting and formatting.