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/syntaxarc/archipy-plugin/archipy-docsnpx skills add SyntaxArc/archipy-plugin --skill archipy-docsgit clone --depth 1 https://github.com/SyntaxArc/archipy-pluginWhat 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.00051 | $0.00502 |
| Opus 5 | $0.00026 | $0.00251 |
| Sonnet 5 | $0.00010 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
archipy-docs 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchiPy Docs Lookup
Procedure
- Read
reference.mdin this skill directory. - Answer from the reference when possible (cite section names).
- If the topic is missing or version-sensitive, point to the matching live doc:
| Topic | URL |
|---|---|
| Docs home | https://syntaxarc.github.io/ArchiPy/ |
| Quickstart | https://syntaxarc.github.io/ArchiPy/getting-started/quickstart/ |
| Project structure | https://syntaxarc.github.io/ArchiPy/getting-started/project_structure/ |
| Adapters | https://syntaxarc.github.io/ArchiPy/tutorials/adapters/ |
| Helpers | https://syntaxarc.github.io/ArchiPy/tutorials/helpers/ |
| Config | https://syntaxarc.github.io/ArchiPy/tutorials/config_management/ |
| DI | https://syntaxarc.github.io/ArchiPy/tutorials/dependency_injection/ |
| Health checks | Bundled reference.md (HTTP + gRPC) + /scaffold-health-checks |
| Errors | https://syntaxarc.github.io/ArchiPy/tutorials/error_handling/ |
| Testing | https://syntaxarc.github.io/ArchiPy/tutorials/testing_strategy/ + /scaffold-bdd |
| Observability | Bundled reference.md § Observability + https://syntaxarc.github.io/ArchiPy/tutorials/observability/ |
| Redis search | Bundled reference.md + /redis-search |
| API reference | https://syntaxarc.github.io/ArchiPy/api_reference/ |
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.
- yesterday First seen · 40 lines · 51 tokens per session scan A 0ec7ce0a00dd
archipy-docs is a skill published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed 8d ago), licensed MIT. It adds 51 tokens to every session and 502 once invoked, about $0.0003 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 skills, from other repositories
specx-component-architecture
Design or review specx core scope boundaries in Python services. Use when deciding where code belongs across packaged scoped foundation bases, optional local foundation extensions, core/, capabilities, delivery, infrastructure, shared/, and ioc; when adding guardrails or splitting use cases, services, DTOs, schemas…
specx-project-structure
Create or reshape a Python FastAPI service repo into the specx clean core/delivery architecture using packaged scoped foundation bases. Use when starting an API backend, adding the first src package, or establishing AGENTS.md, core/, optional local foundation/, delivery/, infrastructure, ioc/, migrations, and tests.
specx-tests
Add or refine tests for specx Python services. Use when creating unit tests for use cases/services, integration tests for FastAPI controllers or infrastructure adapters, e2e smoke tests, architecture import guardrails, DI override tests, pytest fixtures, or coverage and boundary checks.
specx-diwire-composition
Wire dependency injection for a specx Python service with diwire. Use when adding ioc/container.py, explicit dependency registrations for capabilities, repositories, gateways, UoW managers, clients, settings, or factories, Injected[...] constructor fields, FastAPI app factory/lifecycle composition, test overrides, or…
only-skill-you-need
The first and only skill a beginner should install. Bootstraps the rest of the agent skill stack for this project, then routes every task to the current best skill for that job. Keeps a dual ledger (global defaults + project overlay) so the same use-case never gets two skills and a worse skill never replaces a better…
specx-add-core-use-case
Add or refactor a specx core scope use case. Use when implementing an externally meaningful application action under a core scope usecases package, adding same-file command/query inputs, result DTOs, coordinating services, opening a unit-of-work transaction, or moving behavior out of delivery or infrastructure into…