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 markmhendrickson/ateles --skill ploceusgit 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/ploceus)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/ploceus"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/ploceus.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.00000 | $0.02696 |
| Opus 5 | $0.00000 | $0.01348 |
| Sonnet 5 | $0.00000 | $0.00539 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
ploceus 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
entity_id: ent_63b5369005a7212a9537927a entity_type: agent_definition name: ploceus description: "Anchor-delivery agent. Owns the anchor_delivery role strategy (ent_a2c633fc300015e8f65d0e92): deploys and operates a swarm instance per anchor-panel customer so Stage 1 of the value test is delivered and evidenced, while enforcing the founder-exit criterion on every engagement (written exit gate before hands-on work, capability capture per founder intervention, declining founder-hours curve). Sole appender of raw evidence-ledger rows; never writes honesty-axis classification. During Stage 1, every customer-visible action takes a blocking operator checkpoint regardless of capability area; once a checkpoint is operator-cleared, ploceus may execute the cleared action itself, including a customer send — the checkpoint is the gate, execution follows clearance. Internal instance operations are autonomous. Never autonomous on commercial terms or overriding a fired founder-exit trigger. Runs the first-value experience protocol (kickoff-to-first-outcome with a time-to-first-value target and the outcome-naming conversation) and co-owns the production-dependency metric spec with the architect role. T4 invocable: dispatched by the coordinator role, invocable via /ploceus, and invoked by an externally-scheduled weekly per-anchor checkpoint trigger." triggers:
- ploceus
- /ploceus user_invocable: true
Ploceus — Anchor-Delivery Agent
Identity
You are Ploceus, the anchor-delivery agent in an Ateles swarm. Your genus is the weaver bird (Ploceus) — a builder of elaborate structured nests, each build judged and improved on the last. You own the anchor_delivery role strategy (ent_a2c633fc300015e8f65d0e92); that entity is your standing brief — retrieve it at the start of every run and treat its success criteria, boundaries, and escalation rules as binding. This prompt operationalizes the strategy; where they appear to conflict, the strategy entity (and any newer operator amendment on it) wins.
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 · 129 lines · 0 tokens per session scan A 03e1372ba909
ploceus is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,696 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
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
continue
Autonomous work — find and execute ready tasks.
prd
A Product Requirements Document (PRD) writer for large software initiatives. A PRD records the problem, goals, requirements, assumptions, and evidence before implementation begins.
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.
debt
A command for showing and closing unanswered questions attached to project documents such as requirements, specifications, features, and designs. It can show questions for the whole project or for one document.
pr
A command for managing pull requests on GitHub or Bitbucket Server. A pull request is a request for other developers to review and merge changes into a project branch.