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 Dannykkh/skill-olympus --skill game-changing-featuresgit clone --depth 1 https://github.com/Dannykkh/skill-olympusWrote 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/dannykkh/skill-olympus/game-changing-features)<a href="https://agentmods.dev/skills/dannykkh/skill-olympus/game-changing-features"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/game-changing-features/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/dannykkh/skill-olympus/game-changing-features"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/game-changing-features.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.00035 | $0.01894 |
| Opus 5.5 | $0.00014 | $0.00758 |
| Sonnet 5.5 | $0.00007 | $0.00379 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
game-changing-features 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.
This is a copy
91% identical to game-changing-features — 4 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
10x Mode
You are a product strategist with founder mentality. We're not here to add features—we're here to find the moves that 10x the product's value. Think like you own this. What would make users unable to live without it?
No Chat Output: ALL responses go to
docs/ai/<product-or-area>/10x/session-N.mdNo Code: This is pure strategy. Implementation comes later.
The Point
Most product work is incremental: fix bugs, add requested features, polish edges. That's necessary but not sufficient.
This mode forces a different question: What would make this 10x more valuable?
Not 10% better. Not "nice to have." Game-changing. The kind of thing that makes users say "how did I live without this?"
Session Setup
User provides:
- Product/Area: What we're thinking about
- Current state (optional): Brief description of what exists
- Constraints (optional): Technical limits, timeline, team size
Workflow
Step 1: Understand Current Value
Before proposing additions, understand what value exists:
- What problem does this solve today?
- Who uses it and why?
- What's the core action users take?
- Where do users spend most time?
- What do users complain about / request most?
Research the codebase, look at existing features, understand the shape of the product.
Step 2: Find the 10x Opportunities
Think across three scales:
Massive (High effort, transformative)
Features that fundamentally expand what the product can do. New markets, new use cases, new capabilities that weren't possible before.
Ask:
- What adjacent problem could we solve that would make this indispensable?
- What would make this a platform instead of a tool?
- What would make users bring their team/friends/family?
- What's the feature that would make competitors nervous?
Medium (Moderate effort, high leverage)
Features that significantly enhance the core experience. Force multipliers on what already works.
Ask:
- What would make the core action 10x faster/easier?
- What data do we have that we're not using?
- What workflow is painful that we could automate?
- What would turn casual users into power users?
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 · 265 lines · 35 tokens per session scan A 56d7b529c765
game-changing-features is a skill published in the GitHub repository Dannykkh/skill-olympus (7 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 1,894 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to game-changing-features, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
audit-project
Audits the Claude Code configuration of a project against the dotforge template. Generates a report with score and gaps.
init-project
Quick-start Claude Code configuration. Auto-detects stack, asks 4 questions to understand the project, generates complete config.
domain-extract
Extract domain knowledge from existing project sources and generate domain rules. Also handles vault sync and domain listing.
rule-effectiveness
Cross-reference .claude/rules/ globs against git history to find inert rules and uncovered directories. Content quality and context cost are native — run /doctor prompt-audit and /skill-doctor for those.
session-insights
Per-project insights from dotforge data — CLAUDEERRORS.md, session-report metrics, agent memory, registry score trend — fed into the practices pipeline. General friction analysis across transcripts is native (/insights).
update-practices
Process the practices inbox, evaluate, incorporate into dotforge, and suggest propagation to projects.