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/anatomia-dev/anatomia/deploymentnpx skills add anatomia-dev/anatomia --skill deploymentgit clone --depth 1 https://github.com/anatomia-dev/anatomiaWhat 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.00027 | $0.00162 |
| Opus 5 | $0.00014 | $0.00081 |
| Sonnet 5 | $0.00005 | $0.00032 |
| Haiku 4.5 | $0.00003 | $0.00016 |
Grade A, and why
deployment 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.
What it actually says
Deployment
Detected
- CI: GitHub Actions
Rules
- CI runs on 2 runners: Ubuntu × Node 22, 24 with
fail-fast: false. Both must pass. - CI pipeline order: build (includes source typecheck) → typecheck tests → lint → test. If CI fails, check the FIRST failing step — later steps may cascade from an earlier failure. A type error in build will cause test failures downstream.
Gotchas
Not yet captured. Add as you discover them during development.
Examples
Not yet captured. Add short snippets showing the RIGHT way.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 20 lines · 27 tokens per session scan A 43c91fa8314a
deployment is a skill published in the GitHub repository anatomia-dev/anatomia (32 stars, last pushed 29d ago), licensed MIT. It adds 27 tokens to every session and 162 once invoked, about $0.0001 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-30.
Other skills, from other repositories
neus-integrate
Add NEUS access control to a host app. Install the SDK, drop in the gate widget, wire the server check, and test the flow. Use when a developer wants to gate content, sell access, or add proof-based checks to their application.
neus-trust-workflow
Checks identity, permissions, and reusable proofs before sensitive assistant actions. Use when verifying authority, mounting a Trusted Agent, managing Vault secrets, or when the user asks for NEUS Verify.
neus-setup
Add the hosted NEUS endpoint, sign in, and reuse profile, agents, and proofs.
agent-host-e2e-tests
Use when writing, recording, updating, or troubleshooting the agent host end-to-end tests under src/vs/platform/agentHost/test/node/e2e (black-box tests that drive the whole agent host over the AHP protocol, using a CapiReplayProxy record/replay system for Claude/Copilot/Codex). Covers adding a cross-provider test…
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.