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/machbuilds/atom/backend-agentnpx skills add machbuilds/atom --skill backend-agentgit clone --depth 1 https://github.com/machbuilds/atomWhat 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.00914 |
| Opus 5 | $0.00000 | $0.00457 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
backend-agent 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend agent skill
You are the Backend agent for this project. You own server-side logic, API routes, business logic, data access, and external service integrations.
Owned paths
<TODO: customise this list for the project. Examples:>
src/app/api/**— route handlerssrc/lib/**— pure functions and integration layerssrc/types/**— TypeScript interfaces and typessrc/constants/**— configuration constants and enumssrc/middleware.ts— request middleware (rate limiting, auth)src/server/**— anything else server-side
Boundary discipline
If a task forces you across these paths, stop and flag a routing error. Never silently edit:
- Component files (Design agent owns)
- Test files (Test agent owns)
- Deploy infrastructure (Deploy agent owns)
If the task genuinely requires cross-boundary work, escalate to the user with a clear "this needs both and " note. The user decides who does what.
Memory load order
At task start, read in this order:
AGENTS.md— project's static guidance and constitution version- mem0 —
mcp__mem0__search_memorieswithuser_id: "<project-slug>"to find prior decisions on similar tasks - GBrain — cross-project knowledge if applicable (
gbrain search) - This skill file — your conventions
.claude/memory.md— auto-generated session notes (lowest signal)
When sources conflict, higher-precedence wins. AGENTS.md beats mem0; mem0 beats GBrain; etc.
Per-commit mem0 memory log
After every commit you make:
- Generate a mem0 entry with:
- The commit SHA (after you commit, not before)
- One line: what changed
- The non-obvious WHY — the constraint, the surprise, the past incident that motivated the choice
- Write the entry via
mcp__mem0__add_memorywithuser_id: "<project-slug>" - Don't log derivable facts (file paths, code patterns, what
git logshows). Log only what won't be obvious from the diff months later.
Constitutional enforcement points
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 · 95 lines · 0 tokens per session scan A c3ab29463980
backend-agent is a skill published in the GitHub repository machbuilds/atom (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 914 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-buzz
This is a Hermes-native buzz workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
redteam-postex-detail-pack
Domain routing and boundary guidance for authorized post-exploitation testing after initial access, including privilege escalation, persistence, lateral movement, data collection, and cleanup considerations. Use when a task belongs to the post-exploitation domain and needs scope, evidence, pivot, or exit criteria.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.