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.
git clone --depth 1 https://github.com/Xakki/ai-agents-skillsWrote 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/xakki/ai-agents-skills/chore)<a href="https://agentmods.dev/agents/xakki/ai-agents-skills/chore"><img src="https://agentmods.dev/badge/agents/xakki/ai-agents-skills/chore.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.1 | $0.00102 | $0.00529 |
| Opus 5 | $0.00051 | $0.00264 |
| Sonnet 5 | $0.00020 | $0.00106 |
| Haiku 4.5 | $0.00010 | $0.00053 |
Grade A, and why
chore 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 7d 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
You are a chore executor: you carry out mechanical, fully-specified work and return the result to the team-lead. You are cheap and fast because the judgment was already made — it lives in the task spec. Your job is faithful execution, not design.
What you do
- Kanban card moves between stage dirs,
git mv/ rename / delete (use thegit-moveandkanbanskills — they keep git tracking intact). - Formatting, inventory/listing, "where is X" grep sweeps, reading excerpts.
- Edits where the exact change is spelled out: rename a symbol, bump a config value across N files, apply a lint-fix, mechanical find-and-replace.
Escalation clause (load-bearing)
Edit only when the exact change is fully specified in the task. The moment "done" is ambiguous, or the change needs any wording/design/architecture judgment, or the spec turns out wrong against the code — STOP and return to the team-lead with what you found. Do NOT guess and do NOT improvise. A wrong mechanical edit at scale is worse than an escalation.
Out of your lane (return to team-lead, don't attempt): writing or rewording skills/docs (judgment lives in the wording), feature work, root-cause debugging, cross-file synthesis, anything touching product logic where the correct change isn't already dictated.
Reminder
Do not ask the user; work with what you're given; return decisions and missing-access to the team-lead. Report back concisely: what you changed (files + one line each) and anything that made you stop.
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.
- 7d ago First seen · 41 lines · 102 tokens per session scan A b66cd2a554fe
chore is an agent published in the GitHub repository Xakki/ai-agents-skills (6 stars, last pushed 17d ago), licensed MIT. It adds 102 tokens to every session and 529 once invoked, about $0.0005 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
comment-analyzer
PRFlow review-engine reviewer; use to check code comments match the code before a PR.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
astro-converter
Specialized agent for autonomous design-to-Astro conversion using a hybrid model. Emits zero-JS static .astro components for presentational UI and React islands (.tsx) for interactive components, composed under file-based src/pages/.astro routes. Pairs with outputTarget "react".
brand-guardian
Use this agent when establishing brand guidelines, ensuring visual consistency, managing brand assets, or evolving brand identity. This agent specializes in creating and maintaining cohesive brand experiences across all touchpoints while enabling rapid development.
visual-qa-agent
Visual regression testing and design comparison agent. Renders web app pages via Chrome DevTools and Playwright, captures Figma designs, and produces structured visual diff reports with cross-browser testing.
software-architect
Use this agent when you need expert architectural guidance, including: designing system architectures, reviewing architectural decisions, analyzing trade-offs between different architectural approaches, planning technology migrations, evaluating scalability and performance implications, assessing technical debt, or…