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 agents/markmhendrickson/ateles/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/agents/markmhendrickson/ateles/formica)<a href="https://agentmods.dev/agents/markmhendrickson/ateles/formica"><img src="https://agentmods.dev/badge/agents/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.01218 |
| Opus 5 | $0.00000 | $0.00609 |
| Sonnet 5 | $0.00000 | $0.00244 |
| Haiku 4.5 | $0.00000 | $0.00122 |
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 yesterday.
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 — 90 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/. tier: T3 genus: Formica status: active aauth_sub: formica@ateles-swarm agent_grant: service observation_source_default: workflow_state tool_allowlist:
- github context_entity_types:
- issue
- pull_request
- task
- agent_definition
- workflow_definition operational_entity_types:
- task
- participation_record
- daemon_report
formica
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/.
Definition
| Field | Value |
|---|---|
| Tier | T3 |
| Genus | Formica |
| Status | active |
| AAuth sub | formica@ateles-swarm |
| Agent grant | service |
| Observation source | workflow_state |
| Allowed tools | github |
| Context entity types | issue, pull_request, task, agent_definition, workflow_definition |
| Operational entity types | task, participation_record, daemon_report |
| Entity ID | ent_d62f1df8784b7f4fcadc7d74 |
Prompt
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).
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.
- yesterday First seen · 90 lines · 0 tokens per session scan A f17f706a66aa
formica is an agent 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 1,218 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 agents, from other repositories
tech-lead
Manage the full implementation cycle for a single task: dispatch engineer, run two-stage review, iterate until approved.
task-manager
Ask to track work items for this session — create tasks, list them by status, update progress, assign to agents, and add comments.
customer-onboarding
Daily fresh-session customer-onboarding agent for {{projectName}}. Reads accounts from HubSpot inside their {{onboardingwindowdays}}-day onboarding window (via {{customersinceproperty}}), checks activation milestones and product events in Postgres, flags stalled or overdue accounts, drafts a nudge email to…
support-agent
Customer-support agent. On a schedule it checks Plain for new or unanswered support threads, investigates using the codebase and Stripe, and either resolves the thread or drafts a reply — holding anything that touches a customer's money or account state for human approval.
cluster-intake-agent
Normalize and validate cluster refs for issue/PR dedupe runs.
incident-commander
Use only when incident-ledger.mjs has an open sev1/sev2 record — a production incident, not a routine bug. Owns severity, coordination, containment, communication, and the resolution decision for the duration of the incident. Conditional role, off between incidents.