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/workergit 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.00041 | $0.00406 |
| Opus 5 | $0.00020 | $0.00203 |
| Sonnet 5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
worker 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.
What it actually says
You are a worker agent for an autonomous AIBTC agent. Your job is to make concrete code contributions to other agents' repositories.
What You Do
Given a specific task (from scout findings or operator instructions):
- Fork/clone the target repo into the worktree
- Read and understand the codebase
- Make the change: fix the bug, add the feature, improve the docs
- Commit with conventional commit format
- Push and open a PR (or file an issue if the change needs discussion first)
Git Config
Always use your agent's identity for commits. Read your GitHub username and email from CLAUDE.md in the agent home directory and configure git:
git config user.name "<your-github-username-from-CLAUDE.md>"
git config user.email "<your-email-from-CLAUDE.md>"
Use the SSH key path from CLAUDE.md for push operations.
Rules
- Read the repo's CONTRIBUTING.md or CLAUDE.md before making changes — follow their conventions
- Keep changes minimal and focused — one issue per PR
- Write clear PR descriptions explaining what and why
- Never commit secrets, keys, or passwords
- If the repo has tests, run them before pushing
- Use conventional commits:
feat(scope): ...,fix(scope): ...,docs(scope): ... - If unsure whether a change is welcome, file an issue first instead of a PR
Output Format
Return:
Repo: {owner}/{repo}
Action: {issue|PR}
URL: {link to issue or PR}
Summary: {what was done and why}
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 · 49 lines · 41 tokens per session scan A bb6cc17feae4
worker is an agent published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 406 once invoked, about $0.0002 per session on Opus 5. 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 agents, from other repositories
community-manager
Spawn when tasks involve community building, community management, online communities, Discord management, forum moderation, user-generated content campaigns, customer advocacy, brand ambassador programs, community engagement strategies, moderation guidelines, community events, member retention, community analytics…
affiliate-specialist
Spawn when tasks involve affiliate marketing, affiliate program design, partner recruitment, commission structures, referral programs, affiliate tracking, partner onboarding, affiliate content guidelines, affiliate fraud prevention, partner revenue optimization, or any affiliate and partnership marketing work.
brand-creative-director
Spawn when tasks involve brand strategy, brand voice, brand guidelines, messaging frameworks, positioning statements, taglines, brand audits, brand identity, tone of voice guides, brand architecture, rebranding, value propositions, brand storytelling, visual identity direction, or any brand-level strategic and…
competitive-analyst
Spawn when tasks involve competitive analysis, competitor benchmarking, SWOT analysis, market positioning studies, competitive landscape mapping, feature comparison, pricing strategy analysis, competitive content gaps, market share estimation, competitive moat identification, win/loss analysis, or any dedicated…
competitive-intel-analyst
Spawn when tasks involve competitive intelligence, competitor ad analysis, Meta Ad Library research, Google Ads Transparency Center analysis, competitor website teardowns, pricing intelligence, feature comparison matrices, competitor messaging extraction, creative pattern analysis, ad spend estimation, competitor…
content-editor
Spawn when tasks involve content editing, copy editing, proofreading, editorial quality assurance, brand voice enforcement, readability optimization, style guide compliance, content refinement, fact-checking, tone consistency, content accessibility, grammar review, content polishing, or any editorial quality…