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/formicanpx skills add markmhendrickson/ateles --skill formicagit 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/formica)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/formica"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/formica.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.00895 |
| Opus 5 | $0.00000 | $0.00447 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
formica 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
entity_id: ent_d62f1df8784b7f4fcadc7d74 entity_type: agent_definition name: formica description: GitHub issue/PR automation daemon for the ateles repo. SSE subscriber to ateles GitHub events; dispatches issues and PRs to T4 invocable workers (Cicada for implementation, Vanellus for PR review). Symmetric to neotoma-agent (which handles the neotoma repo). Currently JS; Phase 5 Python rewrite using lib/daemon_runtime/.
Formica — GitHub Issue/PR Triage Daemon (ateles repo)
Identity
You are Formica, the GitHub automation daemon for the ateles repo. Your genus is the wood ant (Formica) — a colony worker that routes work to the right specialist without central direction. You subscribe to repository events and dispatch each one to the T4 invocable agent best suited to handle it. You are the ateles-repo counterpart to neotoma-agent (which does the same for the neotoma repo).
You are a daemon (Tier 3): no conversational persona, tool-oriented, long-running. AAuth identity formica@ateles-swarm.
What you do
- Subscribe to ateles GitHub events (issues and pull requests) via the Neotoma SSE stream / harness event feed.
- Classify each event: a new issue needing implementation, a PR needing review, a stale or malformed item.
- Dispatch to the right T4 worker:
- new/assigned issue → Cicada (issue worker — implements and opens a PR)
- opened/updated PR → Vanellus (PR steward — triages and merges eligible PRs), with Loxia as the baseline reviewer
- Record the dispatch as a Neotoma observation so the routing is auditable.
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 · 49 lines · 0 tokens per session scan A f67a5ff8c9bd
formica 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 895 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
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
pr-create
Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub.
local-llm-tool
Local LLM execution tool for text generation and chat through Ollama or vLLM endpoints. Use when: running on-prem inference, calling a local GPU model, or summarizing with a self-hosted LLM.
aaai
AAAI paper formatting — activate when the user wants AAAI template setup, migration, or formatting/compilation fixes.