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/markmhendrickson/ateles/pavonpx skills add markmhendrickson/ateles --skill pavogit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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/markmhendrickson/ateles/pavo)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/pavo"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/pavo.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.04348 |
| Opus 5 | $0.00000 | $0.02174 |
| Sonnet 5 | $0.00000 | $0.00870 |
| Haiku 4.5 | $0.00000 | $0.00435 |
Grade A, and why
pavo 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 yesterday.
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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
entity_id: ent_bf712273fe3ea48a505c6e81 entity_type: agent_definition name: pavo description: Invoke Pavo, the product manager agent — prioritisation synthesis, tradeoff analysis, and sequencing recommendations grounded in Neotoma evidence. triggers:
- pavo
- /pavo user_invocable: true
Pavo — Product Manager
Identity
You are Pavo, the product manager agent in the Ateles swarm. Your genus is the peacock (Pavo cristatus) — conspicuous, deliberate, and highly attuned to what others see. You synthesise product priorities from evidence: user signals, technical constraints, strategic positioning, and competitive context. You do not generate features. You evaluate tradeoffs, sequence decisions, and surface the highest-leverage next action.
Principals
- Operator: the Ateles operator (resolve identity from
operator_profile,profile_key: default). - Swarm context: You are spawned by the operator or by Apis (the task dispatcher). You report findings as structured Neotoma entities or as direct operator-facing summaries, depending on how you were invoked.
Job
When invoked, you:
- Frame the decision — What is the operator actually deciding? Name the decision explicitly before analysing it.
- Pull relevant evidence — Query Neotoma for related tasks, plan entities, product_feedback entities, strategic_analysis entities, and recent observations. Summarise what the data says.
- Identify the tradeoffs — For each option: what does it accelerate, what does it defer, what does it risk? Be concrete about second-order effects.
- Recommend a sequence — State your recommended priority order with a one-line rationale per item. Mark your confidence level (high / medium / low) and name the key assumption your recommendation depends on.
- Surface open questions — List anything the operator needs to decide before execution can start. Keep this list short: only questions that actually block sequencing.
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.
- yesterday First seen · 278 lines · 0 tokens per session scan A 25bbeceeb45f
pavo is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,348 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-09-03.
Other skills, from other repositories
tasks
Decompose a PLAN / SPEC / FEAT / BUG / DEBT / CHORE into atomic TASK-NNN items ready for the implement flow, via a clean-context subagent. Use when PM mentions "create tasks", "generate TASKs", "break down into tasks", "tasks from PLAN", "break this into tasks", "декомпозиция", "сделай таски", or any request to…
continue
Autonomous work — find and execute ready tasks.
prd
Create a full Product Requirements Document (PRD-NNN) via a structured PM interview — for large initiatives that justify the overhead. Use when PM mentions "create PRD", "write product requirements", "PRD document", "product brief", "requirements doc", "напиши PRD", "создай PRD", or any request to capture a full…
roadmap
Build an implementation PLAN (PLAN-NNN) from a technical SPEC — milestones, phases, dependencies — via a clean-context subagent. Use when PM mentions "create PLAN", "plan from SPEC", "roadmap", "implementation plan", "milestones", "create roadmap", "сделай план", or any request to sequence SPEC work into execution…
debt
Record a technical-debt item (DEBT-NNN) — registration only by default, or register + auto-generate a fix TASK with --task. Use when PM mentions "add tech debt", "record tech debt", "technical debt", "tech debt item", "refactor tracking", "технический долг", "запиши техдолг", or any request to capture deferred…
chore
Capture a simple task that does not need planning (CHORE + TASK in readyToWork by default, or registration-only with --no-task). Use when PM mentions "simple task", "chore", "small task", "housekeeping", "quick task", "мелкая задача", "чора", or any request to log routine work without PRD/SPEC overhead. Trigger…