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-business-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-business-perspective)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/from-business-perspective"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/from-business-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-business-perspective"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/from-business-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.00038 | $0.00551 |
| Opus 5 | $0.00019 | $0.00275 |
| Sonnet 5 | $0.00008 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
from-business-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 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.
This is a copy
97% identical to from-business-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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
From business perspective
Contract
| Field | Bound contract |
|---|---|
| Trigger | User wants an answer only from the business seat (money, customers, timing). |
| Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. |
| Side effect | Returns a business-perspective analysis (money, customers, timing) in chat. |
| Done | Returns a business-perspective answer without blending other lenses. |
Inputs
The question or decision to analyze from the business seat. Optional: any supplied context about money, customers, or timing. No external data fetch is required.
Procedure
- Confirm the question is one the business seat can answer in terms of money, customers, or timing. If it is not, stop. Done when: the question is confirmed answerable from the business seat, or the skill stops with a stated mismatch.
- Adopt only the business perspective: revenue, cost, customers, and market timing. Do not import engineering, legal, design, or any other lens. Done when: the analysis is anchored on money, customers, and timing with no imported lens.
- Analyze the question across the three business axes: money (revenue, cost, margin, funding), customers (who pays, who is served, demand, churn), and timing (market window, sequencing, deadlines). Done when: all three axes are addressed.
- Keep the answer self-contained within this lens. Do not blend conclusions from other perspectives mid-answer; comparison across lenses happens only after each lens has produced its own independent output. Done when: no off-lens content appears in the answer.
- Emit the business-perspective answer as chat output. Done when: the answer is emitted as chat output.
Failure and recovery
- Non-business question: if the question cannot be answered from the business seat alone, stop and state that it is outside this lens rather than forcing a business framing.
- Lens bleed: if analysis drifts into another perspective, discard the off-lens content and re-anchor on money, customers, and timing only.
- Missing data: state the missing business fact explicitly rather than inventing figures. Do not pretend the done predicate holds on incomplete evidence.
- Non-mutation: no rollback is needed; this skill produces chat output only.
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.
- 6d ago First seen · 37 lines · 38 tokens per session scan A ee42e1d439db
from-business-perspective is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (36 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 551 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to from-business-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…