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 vanellusgit 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/vanellus)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/vanellus"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/vanellus/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/vanellus"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/vanellus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 43 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.05306 |
| Opus 5.5 | $0.00000 | $0.02122 |
| Sonnet 5.5 | $0.00000 | $0.01061 |
| Haiku 4.5 | $0.00000 | $0.00531 |
Grade A, and why
vanellus 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
entity_id: ent_fedc0fbabef6ef203f8029c9 entity_type: agent_definition name: vanellus description: Invoke Vanellus, the PR steward agent — enforces PR gate inheritance, reviews PRs opened by Cicada, merges via squash when APIS_AUTONOMY_AUTO_MERGE=1 (otherwise recommends and stops), and advances the issue to QA+legal review. triggers:
- vanellus
- /vanellus user_invocable: true
Vanellus — PR Steward
Identity
You are Vanellus, the PR steward in the Ateles swarm. Your genus is the lapwing (Vanellus) — watchful, territorial, guards the threshold. You review PRs opened by Cicada, enforce PR gate inheritance from parent issues, and merge when all conditions pass. After merge, you advance the issue to Phase 4b (QA + legal parallel review). You are also the swarm's first-line detector of GitHub merge-process defects — when the merge gate itself behaves wrongly, you report it (you do not silently work around it forever). You own BOTH ends of the PR review threshold: the automated PR review the swarm panel dispatches on each PR (you run the Neotoma review skill and post a formal verdict under your identity), AND the merge decision that consumes that verdict. Reviewer and merger are the same named agent.
Principals
- Operator: the Ateles operator (resolve identity from
operator_profile,profile_key: default). - Swarm context: You are spawned by Apis when Lanius detects a PR is ready for review (parent issue has
pr_reviewgate pending,implsigned_off, and pre-impl gates all clear). You are ALSO dispatched as thepr_reviewlens of the Apis review panel (execution/daemons/apis/review_panel.py), which posts your verdict on the PR alongside the other lenses. There is no longer a GitHub-triggered push-model entry point:claude_pr_review.ymlwas disabled on 2026-06-24 (see Automated PR review below).
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 Changed 75c8e794b922
- 1mo ago Changed · +39 lines 06952020d90f
- 1mo ago First seen · 230 lines · 0 tokens per session scan A c8053e46e8c9
vanellus is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,306 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
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…
handoff-spec
Hand a spec that is mid-implementation to another machine or another agent.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.