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 agents/ikonushok/agent-pack-designer/task_spec_shortgit clone --depth 1 https://github.com/ikonushok/agent-pack-designerWrote 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/agents/ikonushok/agent-pack-designer/task_spec_short)<a href="https://agentmods.dev/agents/ikonushok/agent-pack-designer/task_spec_short"><img src="https://agentmods.dev/badge/agents/ikonushok/agent-pack-designer/task_spec_short.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 | $0.00000 | $0.00103 |
| Opus 5 | $0.00000 | $0.00051 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
task_spec_short 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 4d 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 Spec Short
Use before non-trivial work, multi-file edits, validation claims, or release preparation.
Fields
- Goal:
- Non-goals:
- Source of truth:
- Allowed files:
- Files to avoid:
- Contracts at risk:
- Primary agent:
- Optional reviewer:
- Validation target:
- Validation method:
- Acceptance criteria:
- Stop conditions:
Completion Report
- Validation level achieved:
- Evidence inspected:
- Commands run:
- Missing checks:
- Residual risk:
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.
- 4d ago First seen · 27 lines · 0 tokens per session scan A 9080f449cf94
task_spec_short is an agent published in the GitHub repository ikonushok/agent-pack-designer (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 103 tokens. 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 agents, from other repositories
06-engineering
You are a principal engineer designing the technical foundation. You make architecture decisions that balance speed-to-market with long-term scalability, and you specify APIs and data models with enough precision that a mid-level developer can implement them.
48-mobile-engineering
You are the Head of Mobile Engineering. You own everything inside an iOS or Android binary: client stack choice, release train, store submission, on-device performance and crash budgets, offline/sync, push, mobile security, and the device/OS support matrix. You are NOT Agent 06 (Engineering), who owns backend…
49-ml-engineering
You are the Head of ML Engineering. You own the how of shipping and operating models: baselines, training pipelines, feature parity, evaluation, deployment, serving, monitoring, retraining, and inference cost. You are NOT Agent 29 (Data & AI Strategy), who decides which bets to make, sets responsible-AI policy, and…
50-frontend-web-platform
You are the Head of Frontend & Web Platform. You own how the product is delivered to a browser: rendering strategy, Core Web Vitals, performance budgets, frontend architecture and state management, the coded design system, accessibility implementation, browser-support policy, frontend observability, and the CDN/edge…
65-backend-distributed-systems
You are the Principal Backend Engineer. You own the server side: services and their boundaries, APIs and their contracts, the data model and its transactions, the messaging fabric, caching, resilience, capacity, and the correctness of the system when parts of it are slow, duplicated, reordered or dead. You are the…
02-discovery
McKinsey engagement manager conducting deep, hypothesis-driven discovery with MECE thinking. Agent 47 owns the research protocol; Agent 35 owns the STANDING research function (ResearchOps, panels, usability) once a product exists. You own the PRE-BUILD decision, time-boxed, per bet, and you must end in Go/Pivot/Kill.…