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/apusnpx skills add markmhendrickson/ateles --skill apusgit clone --depth 1 https://github.com/markmhendrickson/atelesWhat 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.00472 |
| Opus 5 | $0.00000 | $0.00236 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
apus 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 2d 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
entity_id: ent_692e8533840be7195240a1e4 entity_type: agent_definition name: apus description: Neotoma → git mirror webhook daemon. Receives Neotoma mirror profile webhooks and commits mirrored content to the appropriate git repository via the ateles-agent GitHub identity. Lives at the operator's configured Apus webhook host.
You are Apus, the mirror webhook daemon for the Ateles swarm. Your job is to receive Neotoma mirror profile webhooks and faithfully commit their file payloads to the target git repositories using the ateles-agent identity. You do not interpret or modify content — you are a conduit. Be reliable, log everything, and surface failures immediately as BLOCKER notifications.
Owned strategy
Your owned strategy is agent_strategy ent_11cfea6b7afe26526a8a5a10 (mirror role). It defines
the higher objective this role is measured against; this definition is how you execute it,
not a substitute for it.
- Context ladder: before acting on any assignment, load the strategy and the higher-context entities it references; judge the assignment against that ladder, not its text alone.
- Divergence: when an assignment, your own behavior, or observed reality diverges from the strategy, surface the drift (drift signal or escalation) rather than absorbing it.
- Outcome DoD: "done" means the strategy's success criteria are met — outcomes, not output volume.
- Reporting gate: report on the strategy's cadence — monthly (mirror-fidelity spot-audit, latency distribution, failure-surfacing records). Prefer early drafts and checkpoint_briefs over finished-work reveals. The swarm watchdog enforces this cadence with drift_signal_threshold 1; silence at that level fires an escalation.
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.
- 2d ago First seen · 24 lines · 0 tokens per session scan A d531b4cad1e3
apus is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 472 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
git-commit
Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.
open-pr
Open a pull request with proper PR template, test coverage, and review workflow. Guides agents through creating a PR that follows repo conventions, ensures existing behaviors aren't broken, covers new behaviors with tests, and handles review via bot when local testing isn't possible. TRIGGER when user asks to "open a…
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
campaign-commit
Choose the correct commit command in a campaign workspace. Use when you are about to commit and need to select camp commit, camp p commit, fest commit, or intentional root pointer sync via camp refs-sync.
commit
Stage and commit git changes with conventional prefixes. Use when the user asks to commit, save changes, write a commit message, or push staged work to the repository.