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 OutlineDriven/odin-claude-plugin --skill from-breaking-perspectivegit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/outlinedriven/odin-claude-plugin/from-breaking-perspective)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/from-breaking-perspective"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/from-breaking-perspective/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/outlinedriven/odin-claude-plugin/from-breaking-perspective"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/from-breaking-perspective.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.00043 | $0.00541 |
| Opus 5 | $0.00022 | $0.00270 |
| Sonnet 5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
from-breaking-perspective 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 3d 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.
This is a copy
92% identical to from-breaking-perspective — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
From breaking perspective
Contract
| Field | Bound contract |
|---|---|
| Trigger | User wants an answer only from the breaking seat (stakeholders, dependencies, accounting, compatibility under destructive pressure). |
| Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. |
| Side effect | Returns a breaking-perspective analysis in chat. |
| Done | Returns a breaking-perspective answer without blending. |
Inputs
The subject to analyze (a decision, design, change, or situation). Optional: the specific destructive pressure to apply (cost, removal, dependency failure, stakeholder withdrawal). Everything else is derived from the subject.
Procedure
- Identify the subject and the destructive pressure the user named. If the user named none, apply the full breaking seat: stakeholders, dependencies, accounting, and compatibility under destructive pressure. Done when: the subject and destructive pressure are identified, or the full seat is applied by default.
- Answer only from the breaking seat. Treat the subject as if the destructive pressure is actually applied: which stakeholders break, which dependencies fail, what the accounting shows under loss, and what stays compatible when parts are removed. Done when: the breaking-seat analysis covers stakeholders, dependencies, accounting, and compatibility.
- Do not blend other perspectives (business, codebase, impact, career, rent-seeking, innovation, stability, moat, human, skeptic) into the answer. Each lens answers only from its named seat; lenses are compared after their independent outputs, never mid-answer. Done when: no content from another lens appears in the answer.
- Stop when the breaking-seat analysis is complete. Do not recommend a decision or reconcile with other lenses; that is a later comparison step outside this skill. Done when: the analysis is complete with no recommendation or cross-lens reconciliation.
Failure and recovery
- Blended answer: if the output mixes another lens, restart from step 2 and remove the non-breaking content. The done predicate requires no blending.
- Missing subject: if no subject is supplied, ask for one. Do not invent a subject.
- No destructive pressure named and none derivable: apply the full breaking seat by default; this is not a failure.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 35 lines · 43 tokens per session scan A 1c45dbe128dd
from-breaking-perspective is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed 2d ago), licensed Apache-2.0. It adds 43 tokens to every session and 541 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to from-breaking-perspective, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…