Borrowing it
Nothing to install: this file belongs to saski/arnesto. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saski/arnesto/main/.agents/skills/seven-powers/SKILL.mdgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/seven-powers)<a href="https://agentmods.dev/skills/saski/arnesto/seven-powers"><img src="https://agentmods.dev/badge/skills/saski/arnesto/seven-powers.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.1 | $0.00070 | $0.00519 |
| Opus 5 | $0.00035 | $0.00260 |
| Sonnet 5 | $0.00014 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
seven-powers 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
100% identical to seven-powers — 0 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
7 Powers: The Foundations of Business Strategy
What It Is
7 Powers is a framework for understanding sustainable competitive advantage. The core insight: Business value comes from possessing an attribute that produces higher returns than competitors AND a barrier that prevents competitors from arbitraging it away.
Power = Benefit + Barrier
Warren Buffett famously said: "In business, I look for economic castles protected by unbreachable moats." Power is understanding what makes something a castle (the benefit) versus a shack, and what makes the moat unbreachable (the barrier).
The key shift: Move from asking "What's our competitive advantage?" to asking "What economic structure creates durable differential returns?"
When to Use It
Use 7 Powers when you need to:
- Evaluate a business's long-term defensibility (investment decisions, competitive analysis)
- Design a startup for durability (not just product-market fit)
- Understand why incumbents can't respond to your disruptive move
- Prioritize strategic initiatives based on what builds power
- Identify whether you actually have a moat or just operational excellence
- Plan second acts (new business lines that could develop power)
- Win market share battles in high-growth phases
When Not to Use It
- You don't have product-market fit yet
- The business is purely commodity with no differentiation possible
- You want to justify a strategy you've already decided on
- You're optimizing operations (power is about structure, not execution)
Resources
Books:
- 7 Powers by Hamilton Helmer
- Good Strategy Bad Strategy by Richard Rumelt
- Competition Demystified by Bruce Greenwald
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 · 59 lines · 70 tokens per session scan A 9d300a738abb
seven-powers is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 70 tokens to every session and 519 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seven-powers, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.