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 jeffreytse/grimoire-core --skill apply-extreme-ownershipgit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/apply-extreme-ownership)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-extreme-ownership"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-extreme-ownership/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/jeffreytse/grimoire-core/apply-extreme-ownership"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-extreme-ownership.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.00049 | $0.01808 |
| Opus 5 | $0.00024 | $0.00904 |
| Sonnet 5 | $0.00010 | $0.00362 |
| Haiku 4.5 | $0.00005 | $0.00181 |
Grade A, and why
apply-extreme-ownership 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Extreme Ownership
Accept full responsibility for all outcomes in your domain — including failures caused by your team members — by treating every shortfall as a failure of your leadership (inadequate training, unclear direction, wrong priorities, poor selection) rather than a failure of the individual, and acting on that attribution.
Why This Is Best Practice
Adopted by: Core methodology of US Navy SEAL leadership training; the approach was developed and tested across multiple combat deployments before being formalized by Jocko Willink and Leif Babin in "Extreme Ownership" (2015, over 1M copies sold). Echelon Front (Willink and Babin's leadership consulting firm) has trained Fortune 500 companies including Walmart, Fidelity, and Cargill. Widely taught in military officer development programs (US Marine Corps officer training explicitly covers the "no bad teams, only bad leaders" principle). Andy Grove applied a similar ownership framework at Intel, documented in "High Output Management" (1983). Impact: Ng, Sorensen & Eby (2006) Journal of Organizational Behavior — meta-analysis of 135 studies: leaders with internal locus of control (who attribute outcomes to their own actions rather than external factors) produce significantly better team performance, higher subordinate motivation, lower turnover, and higher engagement. Cohen's d = 0.34 across performance outcomes. Bandura (1997) self-efficacy research: leaders who model ownership behavior increase team self-efficacy and accountability behaviors in subordinates through observational learning — the leader's attribution behavior becomes the team's attribution behavior. Military data: SEAL platoons led by ownership-oriented leaders consistently outperformed technically superior platoons led by blame-oriented leaders across evaluated missions. Why best: The alternative — attributing team failures to team members — is the default human response and produces a predictable dysfunctional loop: leader assigns blame → team member becomes defensive → root cause is not examined → same failure recurs. Extreme ownership breaks this loop by forcing the leader to examine their own decisions: Did I train them properly? Did I give clear direction? Did I set the right priorities? Did I select the right person for this task? These questions have actionable answers. "The team member failed" has no actionable answer.
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.
- 8d ago First seen · 117 lines · 49 tokens per session scan A 3a587af74f61
apply-extreme-ownership is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 49 tokens to every session and 1,808 once invoked, about $0.0002 per session on Opus 5. 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-09-03.
Other skills, from other repositories
org-report
Generate an executive organization brief (leadership chain, direct reports, extended teams, and vendor partners) for a target person. Produces a Word + PDF report from a directory MCP source (WorkIQ is the reference implementation) and displays it in a Copilot canvas. Triggers on "generate org report for X", "build…
coaching-techniques
GROW model, active listening, developmental feedback, and team growth approaches.
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
stakeholder-management
Influence mapping, communication strategies, and expectation management for complex organizations.
scaffolding-generator
Pattern-aware code scaffolding that detects existing conventions and generates new components matching the codebase style. Use when asked to "scaffold a component", "generate boilerplate", "create a new module", "bootstrap a service", "add a new endpoint", "create a new controller", or "add a new feature module".…
status-reporting
Create stakeholder-friendly project status updates and progress reports.