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 Eliyce/paqad-ai --skill request-classifiergit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/request-classifier)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/request-classifier"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/request-classifier.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.00014 | $0.00570 |
| Opus 5 | $0.00007 | $0.00285 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
request-classifier 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 7d 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.
What it actually says
What It Does
Produces a deterministic request classification across the routing dimensions used by the framework so downstream skill and rule selection can rely on explicit signals instead of guesswork.
Use This When
Use this at the start of a new request or whenever the effective scope changed enough that prior routing assumptions may no longer be safe.
Inputs
- Read the request text, attached plan, and any directly linked issue or spec.
- Read the nearest canonical docs only when they clarify stack, module, or risk signals.
- Read
references/decision-rules.mdbefore assigning ambiguous dimension values.
Procedure
- Pipe the raw request into
scripts/extract-signals.shto get baseline keyword-derived dimensions (workflow, ui/api/db impact, scope, risk hint). - Override script defaults only when canonical evidence (linked spec, stack manifest, module map) contradicts them — record the override under Evidence.
- Use
assets/dimensions.txtfor the allowed value set per dimension. - Default to most conservative accurate value when ambiguous; never invent certainty for risk/sensitivity.
- Format per
assets/output.template.md; validate withscripts/lint-output.sh.
Output Contract
- Match
assets/output.template.md:## Classification(onekey: valueper dimension) and## Evidence(bullet list for non-obvious calls). - Output must pass
scripts/lint-output.sh(exit 0).
Escalate / Stop Conditions
- Ask when stack, workflow, or impact dimensions cannot be inferred safely from the request.
- Warn when canonical docs contradict the request about modules, interfaces, or current behavior.
- Do not fabricate certainty for risk or sensitivity dimensions.
Resources
references/decision-rules.mdscripts/extract-signals.shscripts/lint-output.shassets/output.template.mdassets/dimensions.txtruntime/base/skills/existing-doc-checker/SKILL.mdagents/openai.yaml
What ships with it
6 files 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.
- 7d ago First seen · 74 lines · 14 tokens per session scan A a9e70c760f70
request-classifier is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 570 once invoked, about $0.0001 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-31.
Other skills, from other repositories
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.
agent-pipeline
Multi-agent pipeline orchestration skill.