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 dev-toolings/superpowers-symfony --skill effective-contextgit clone --depth 1 https://github.com/dev-toolings/superpowers-symfonyWrote 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/dev-toolings/superpowers-symfony/effective-context)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/effective-context"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/effective-context/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/dev-toolings/superpowers-symfony/effective-context"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/effective-context.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.00021 | $0.00340 |
| Opus 5.5 | $0.00008 | $0.00136 |
| Sonnet 5.5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
effective-context 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 23d 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
88% identical to brainstorming — 36 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.
What it actually says
Effective Context (Symfony)
Use when
- Asking for help on a Symfony problem, or handing a task over to someone else.
- A previous answer was wrong because versions, bundles or constraints were missing.
- Reporting an error that needs diagnosis.
Default workflow
- State the goal and the expected behavior in one or two sentences.
- Give the versions: Symfony, PHP, and the bundles involved.
- Include only the files on the path of the problem: entity, service, controller, configuration.
- Paste the full error with its stack trace, and the relevant log lines.
- List the constraints (performance, backward compatibility, existing patterns) and what was already tried.
Guardrails
- Send the code on the path of the problem: not the whole
src/, not a bare one-line question. - Do not refer to code that was not shown.
- Strip secrets and personal data from logs and
.envexcerpts.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- A context block following the template in
reference.md: context, goal, current code, observed behavior, attempts, constraints. - Versions and bundles, stated explicitly.
References
reference.md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago Changed 03fa14f1fc24
- 1mo ago Changed · +2 lines · -1 tokens per session b4408e0c1877
- 1mo ago First seen · 40 lines · 22 tokens per session scan A 0852bc3072a2
effective-context is a skill published in the GitHub repository dev-toolings/superpowers-symfony (227 stars, last pushed 23d ago), licensed MIT. It adds 21 tokens to every session and 340 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to brainstorming, differing in 36 lines, and is treated as a copy.
Other skills, from other repositories
servicenow-expert
Expert in ServiceNow platform development, scripting, workflows, Service Portal, CMDB, ITSM modules, and integrations. Use when the user mentions ITSM, ITOM, workflow, automation, CMDB, or service portal, or when the task involves ServiceNow Platform, Development Components, Scripting APIs, or GlideRecord Query and…
spine-design
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
warden-harden
Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".
cortex-integrate
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
spine-api
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
spine-perf
Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".