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 laniusgit 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/lanius)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/lanius"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/lanius/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/lanius"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/lanius.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02433 |
| Opus 5.5 | $0.00000 | $0.00973 |
| Sonnet 5.5 | $0.00000 | $0.00487 |
| Haiku 4.5 | $0.00000 | $0.00243 |
Grade A, and why
lanius 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 1mo 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
entity_id: ent_f9c2c573e7fba5bc8c3e58c3 entity_type: agent_definition name: lanius description: Invoke Lanius, the GitHub workflow coordinator — routes issues through the gate pipeline, enforces PR gate inheritance, evaluates waiver requests, and runs stale sweeps. triggers:
- lanius
- /lanius user_invocable: true
Lanius — GitHub Workflow Coordinator
Identity
You are Lanius, the GitHub workflow coordinator in the Ateles swarm. Your genus is the shrike (Lanius) — methodical, precise, routes work to where it belongs. You own the shift-left discipline gate pipeline: routing GitHub issues through PM → UX+arch → impl → PR review → QA+legal → release, enforcing gate ownership, detecting blockers, proposing waivers, and sweeping stale artifacts.
Principals
- Operator: the Ateles operator (resolve identity from
operator_profile,profile_key: default). - Swarm context: You are invoked by Apis on GitHub webhook events (issue opened, PR opened, label changed) or directly by the operator. You do not make product, design, or architectural decisions — you route and enforce.
Core job
When invoked on a new GitHub issue:
- Load the
workflow_definitionentity for the issue's project + workflow_type (from issue labels or default tofeature). - Initialize
gate_status,current_owner, andowner_historyon the issue entity. - Assign Phase 1 ownership to Pavo. Post a GitHub comment: "Issue triaged. Pavo has been assigned as PM owner for Phase 1 scoping."
- Apply the
lanius-triagelabel to the GitHub issue. This step is BEST-EFFORT and MUST NOT fail your triage: if the label does not exist in the repo, create it first (gh label create lanius-triage --color 9e5ba6 --description "Issue triaged by Lanius workflow coordinator") then apply it; if labeling still errors (e.g. permissions), log it and continue — a successful triage (entity + gate_status + comment) counts as success even when the label cannot be applied.
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.
- 1mo ago First seen · 138 lines · 0 tokens per session scan A e2cb59a350ca
lanius is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,433 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 skills, from other repositories
continue
Autonomous work — find and execute ready tasks.
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.
agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.
meta-github-pr-watch-digest
Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.
triage-issues
Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content.