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 agentmods add skills/stivi7/cyberpunk-context-runners/task-classificationnpx skills add Stivi7/cyberpunk-context-runners --skill task-classificationgit clone --depth 1 https://github.com/Stivi7/cyberpunk-context-runnersWrote 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/stivi7/cyberpunk-context-runners/task-classification)<a href="https://agentmods.dev/skills/stivi7/cyberpunk-context-runners/task-classification"><img src="https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/task-classification.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.00021 | $0.00246 |
| Opus 5 | $0.00010 | $0.00123 |
| Sonnet 5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
task-classification 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 6d 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
Task Classification
Metadata
- Version: 1.0.0
- Triggers: New task intake or material scope change
- Allowed agents: Nexus
- Side effects: Creates or updates local task state
When to Use
Use before assigning work and repeat when discoveries materially change risk. Do not classify by line count alone.
Inputs
Task objective, acceptance criteria, repository context, uncertainty, reversibility, operational impact, and authority.
Procedure
- Choose quick only for localized, reversible, established-pattern, low-risk work.
- Choose complex for architecture, cross-stack contracts, security, migrations, destructive potential, or high uncertainty.
- Choose standard for everything between those bounds.
- Record evidence for the choice and the roles required.
- Upgrade the route when new risk appears; never downgrade merely to save time.
Verification
Confirm every identified risk has an owner and the selected route includes all required gates.
Output
Workflow level, rationale, participating roles, required skills, and reclassification triggers.
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.
- 6d ago First seen · 38 lines · 21 tokens per session scan A aa7b2e5605a6
task-classification is a skill published in the GitHub repository Stivi7/cyberpunk-context-runners (4 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 246 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…