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 CodedRichy/food-chain-ideation --skill apex-to-actiongit clone --depth 1 https://github.com/CodedRichy/food-chain-ideationWrote 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/codedrichy/food-chain-ideation/apex-to-action)<a href="https://agentmods.dev/skills/codedrichy/food-chain-ideation/apex-to-action"><img src="https://agentmods.dev/badge/skills/codedrichy/food-chain-ideation/apex-to-action/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/codedrichy/food-chain-ideation/apex-to-action"><img src="https://agentmods.dev/badge/skills/codedrichy/food-chain-ideation/apex-to-action.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.00089 | $0.01667 |
| Opus 5.5 | $0.00036 | $0.00667 |
| Sonnet 5.5 | $0.00018 | $0.00333 |
| Haiku 4.5 | $0.00009 | $0.00167 |
Grade A, and why
apex-to-action 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apex to Action
What This Is
A execution planner that takes battle-tested output from food-chain-ideation and converts it into a 90-day plan with validation gates, weekly milestones, and a kill list.
What This Is Not
- Not a project management tool. No Gantt charts, no sprint planning, no resource allocation.
- Not a generic business plan generator. It only works on ideas that survived a food chain battle.
- Not a replacement for judgment. It gives you structure, not answers.
Input Requirements
Minimum required: Evolved Idea + Unfair Advantage Statement.
Strongly preferred: Full Battle Log block from food chain output (includes fallen animals, patches applied, killed features).
If the user does not have battle output, respond:
You need a battle-tested idea first. Run
/food-chain-ideationwith your raw idea, then come back with the output. This skill only works on ideas that survived the food chain.
If the user pastes a Battle Log, parse every field: original idea, evolved idea, apex predator, patches, fallen animals, killed features, unfair advantage.
Step 1 — Battle Debrief
Parse the battle output and produce:
## Battle Debrief
| Field | Value |
|---|---|
| **Original idea** | [extracted from battle output] |
| **Evolved idea** | [extracted — this is what we're planning for] |
| **Apex predator** | [what survived and why it won] |
| **Key patches applied** | [list of adaptations made during battle] |
| **Killed features** | [features that lost every round — these go on the kill list] |
| **Unfair advantage** | [extracted — this drives Phase 2 build priority] |
Extract killed features from fallen animals' insights. Each fallen animal likely attacked a weakness — the patches that stuck are strengths, the features that kept failing are dead.
Step 2 — Validation Gates
Things that must be proven TRUE before writing any code. Each gate is a specific, binary test.
## Validation Gates — prove these before writing code
| Gate | Test | Pass if | Method |
|---|---|---|---|
| 1 | [specific test] | [measurable criterion] | [how to run the test] |
| 2 | [specific test] | [measurable criterion] | [how to run the test] |
| 3 | [specific test] | [measurable criterion] | [how to run the test] |
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 · 185 lines · 89 tokens per session scan A ce9b35285895
apex-to-action is a skill published in the GitHub repository CodedRichy/food-chain-ideation (3 stars, last pushed 3d ago), licensed MIT. It adds 89 tokens to every session and 1,667 once invoked, about $0.0004 per session on Opus 5.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-08-31.
Other skills, from other repositories
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…
change-management
Framework for rolling out organizational changes without chaos. Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes. Use when announcing a reorg, switching tools…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…