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 hekivo/superpowers-sage --skill modelinggit clone --depth 1 https://github.com/hekivo/superpowers-sageWrote 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/hekivo/superpowers-sage/modeling)<a href="https://agentmods.dev/skills/hekivo/superpowers-sage/modeling"><img src="https://agentmods.dev/badge/skills/hekivo/superpowers-sage/modeling.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.00066 | $0.01005 |
| Opus 5 | $0.00033 | $0.00502 |
| Sonnet 5 | $0.00013 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
superpowers-sage:modeling 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modeling — Content Architecture Analysis
Classify content within blocks and components to determine the right data modeling approach: static ACF fields, dynamic CPTs, Options Pages, or relationship fields.
When to use
- Planning a new block or component that displays content
- Deciding whether content should be hardcoded, editable per-page, or managed as a collection
- Before implementing blocks to prevent "static content that should be dynamic" mistakes
- Automatically invoked by
/buildingwhen content classification is needed
Content Classification Matrix
| Classification | When to Use | Implementation |
|---|---|---|
| Static | Fixed text that rarely changes, part of page identity | ACF field in block fields() |
| Dynamic Collection | Growing list of items (portfolio, team, testimonials) | CPT via Poet + taxonomy |
| Dynamic Global | Shared across pages (site info, social links, CTA) | ACF Options Page |
| Dynamic Relation | References other content (featured posts, related projects) | ACF Relationship field |
| Fixed Repeater | 3-5 items, rarely change, no detail pages | ACF Repeater field in block |
Decision Checklist
For each piece of content in a block, ask:
-
Does this content appear in more than one place?
- YES → Dynamic Global (Options Page) or Dynamic Relation
- NO → Continue...
-
Will the client add/remove items over time?
- YES → Dynamic Collection (CPT)
- NO → Continue...
-
Does the list have categories or filters?
- YES → Dynamic Collection (CPT + taxonomy)
- NO → Continue...
-
Is it a fixed set of 3-6 items that rarely changes?
- YES → Fixed Repeater (ACF Repeater in block)
- NO → Continue...
-
Does this content have its own detail page?
- YES → Dynamic Collection (CPT) — even if the list is short
- NO → Continue...
-
Should this content be searchable or filterable on the frontend?
- YES → Dynamic Collection (CPT)
- NO → Static (ACF field)
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 · 124 lines · 66 tokens per session scan A 927e42f9208f
superpowers-sage:modeling is a skill published in the GitHub repository hekivo/superpowers-sage (13 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 1,005 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.
common-observability
Enforce structured JSON logging, OpenTelemetry distributed tracing, and RED metrics across backend services. Use when adding request correlation, setting up tracing spans, defining SLO burn-rate alerts, or instrumenting middleware.