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 oliver-kriska/claude-elixir-phoenix --skill intent-detectiongit clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenixWrote 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/oliver-kriska/claude-elixir-phoenix/intent-detection)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/intent-detection"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/intent-detection/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/oliver-kriska/claude-elixir-phoenix/intent-detection"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/intent-detection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01287 |
| Opus 5.5 | $0.00022 | $0.00515 |
| Sonnet 5.5 | $0.00011 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
intent-detection 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Detection — Workflow Routing
When user describes work WITHOUT specifying a /phx: command, analyze their intent and suggest the appropriate workflow BEFORE starting work.
Hard guard — check FIRST: if the message starts with any slash command
(/phx:, /ecto:, /lv:, or any other /command), this skill does not apply.
Follow the invoked command directly — no routing analysis, no suggestion, zero
output from this skill.
Routing Table
| Signal | Detected Intent | Suggest |
|---|---|---|
| "bug", "error", "crash", "failing", "broken", stack trace | Bug investigation | /phx:investigate |
| "brainstorm", "explore idea", "not sure what I need", "vague idea", "let's discuss", "how to approach" | Ideation/requirements | /phx:brainstorm |
| "add", "implement", "build", "create" + multi-step | New feature | /phx:plan |
| "review", "check", "audit" code | Code review | /phx:review |
| "fix" + small/specific scope | Quick fix | handle directly or /phx:quick |
| "refactor", "clean up", "improve" | Refactoring | /phx:plan (needs scope) |
| "research", "how to", "what's the best" | Research | /phx:research |
| "evaluate", "compare", "adopt", "library", "should we use" | Library evaluation | /phx:research --library |
| "test", "spec", "coverage" | Testing | handle directly or /phx:plan |
| Describes 1-2 file changes, < 50 lines | Small task | handle directly |
| "deploy", "release", "production" | Deployment | /phx:verify then deploy |
| "performance", "slow", "N+1", "memory" | Performance | /phx:perf |
| "PR review", "review comments", "address feedback", "respond to PR" | PR response | /phx:pr-review |
| "that worked", "fixed it", "problem solved" | Knowledge capture | /phx:compound |
| "enhance plan", "more detail", "deepen" | Plan enhancement | /phx:plan --existing |
| "triage", "which findings", "prioritize fixes" | Finding triage | /phx:triage |
Behavior
- Read user's first message
- Match against routing table (use keyword + context signals, not exact match)
- If match found with multi-step workflow: "This looks like [intent]. I'd suggest
[command]— want me to run it, or should I just dive in?" - If trivial task (typo, single-line fix, config change): skip suggestion, just do it
- If user already specified a
/phx:command: follow it, don't re-suggest - NEVER block the user — suggestion only, not mandatory
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 · 111 lines · 55 tokens per session scan A fe27db3bbcd2
intent-detection is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (567 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 1,287 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
craft-content-modeling
Craft CMS 5 content modeling — sections, entry types, fields, Matrix, relations, project config, and content architecture strategy. Covers choosing section types, designing entry types and field layouts, selecting field types, configuring Matrix and nested entries, relations and eager loading, and multi-site…
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
craft-php-guidelines
Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers…
craft-twig-guidelines
Twig coding standards and conventions for Craft CMS 5 templates. ALWAYS load this skill when writing, editing, or reviewing any .twig file in a Craft CMS project — even for small edits. Covers: variable naming (camelCase, no abbreviations), null handling (?? operator, ??? with empty-coalesce plugin), whitespace…
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
craft-plugin-release
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…