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/prikotov/task-agents-playbook/questionsgit clone --depth 1 https://github.com/prikotov/task-agents-playbookWrote 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/prikotov/task-agents-playbook/questions)<a href="https://agentmods.dev/agents/prikotov/task-agents-playbook/questions"><img src="https://agentmods.dev/badge/agents/prikotov/task-agents-playbook/questions.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.00037 |
| Opus 5 | $0.00000 | $0.00018 |
| Sonnet 5 | $0.00000 | $0.00007 |
| Haiku 4.5 | $0.00000 | $0.00004 |
Grade A, and why
questions 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 5d 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
Вопросы для выявления навыков
Git Workflow
- Когда ты приступаешь к задаче, в какой момент ты создаешь ветку в репозитории?
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.
- 5d ago First seen · 6 lines · 0 tokens per session scan A 34f6a71e1b4d
questions is an agent published in the GitHub repository prikotov/task-agents-playbook (21 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 37 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-30.
Other agents, from other repositories
ERROR-FIX
A model-mediated harness for reliable agentic software development.
namba-designer
Use this role when art direction, palette/tone logic, composition, motion intent, or generic-looking UI surfaces need to be clarified before implementation or review. State effect: read-only. Do not edit repository files.
namba-backend-architect
Use this role when backend contracts, service boundaries, or persistence changes need to be clarified before implementation. State effect: read-only. Do not edit repository files.
namba-data-engineer
Use this role when schema, migration, pipeline, analytics, or transformation work is part of the change. State effect: workspace-write. Edit only files assigned by the main session.
agent-builder
Generates a new, complete Claude Code sub-agent configuration file from a user's description. Use this to create new agents. Use this Proactively when the user asks you to create a new sub agent, or uses the '/agents' command. When you prompt this agent, include the user's prompt VERBATIM. Remember, this agent has no…
observability-engineer
Expert consultant for monitoring, logging, distributed tracing, and alerting for backend systems, providing analysis and recommendations without writing code. Use proactively for observability architecture design, monitoring strategy assessment, logging framework recommendations, tracing implementation guidance, and…