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 skills add SyntaxArc/archipy-plugin --skill scaffold-archipy-domaingit clone --depth 1 https://github.com/SyntaxArc/archipy-pluginWrote 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/skills/syntaxarc/archipy-plugin/scaffold-archipy-domain)<a href="https://agentmods.dev/skills/syntaxarc/archipy-plugin/scaffold-archipy-domain"><img src="https://agentmods.dev/badge/skills/syntaxarc/archipy-plugin/scaffold-archipy-domain.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.00043 | $0.01170 |
| Opus 5 | $0.00022 | $0.00585 |
| Sonnet 5 | $0.00009 | $0.00234 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
scaffold-archipy-domain 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 today.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold ArchiPy Domain
Before writing files
- Inspect
pyproject.toml, the package tree, neighboring domains, DI containers, and existing tests. - Infer package name, installed extras, naming, transport, and sync/async style from the repository.
- Ask only for unresolved choices that materially change the generated slice:
- Domain name
- Missing infrastructure/extras
- Transport when the app does not already establish one (default FastAPI)
- Preserve existing files. Extend compatible modules; stop and explain conflicts instead of overwriting them.
Compose — do not fork templates
Before generating files, read these plugin skills in full:
../scaffold-archipy-adapter/SKILL.md../scaffold-archipy-logic/SKILL.md../scaffold-archipy-service/SKILL.md
Apply their constraints and Verify sections in order; do not replace them with summaries:
- Models — stubs below, then flesh via
using-archipy-modelsrule - scaffold-archipy-adapter — thin wrapper under
repositories/<domain>/adapters/+<domain>_repository.py - scaffold-archipy-logic — at least one use-case under
logics/<domain>/ - scaffold-archipy-service —
services/<domain>/v1/<domain>_service.py
Install extras as needed: uv add "archipy[<extras>]".
Model stubs (create first)
models/
├── dtos/<domain>/
│ ├── domain/v1/
│ │ ├── <domain>_input_dto.py
│ │ └── <domain>_output_dto.py
│ └── repository/
│ └── <domain>_command_dto.py
├── errors/
│ └── <domain>_errors.py
└── entities/ # optional
└── <domain>_entity.py
Example shapes (order → rename):
# models/dtos/order/domain/v1/order_create_input_dto.py
from pydantic import Field
from archipy.models.dtos.base_dtos import BaseDTO
class OrderCreateInputDTO(BaseDTO):
"""Domain input crossing the service → logic boundary."""
customer_id: str = Field(min_length=1)
sku: str = Field(min_length=1)
quantity: int = Field(gt=0)
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.
- today Changed · +17 lines b7aafade64b1
- 7d ago First seen · 122 lines · 43 tokens per session scan A 4f3c52bcbd19
scaffold-archipy-domain is a skill published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,170 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 skills, from other repositories
fastapi-templates
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
telnyx-numbers-python
Search, order, and manage phone numbers by location, features, and coverage.
telnyx-ai-outbound-voice-python
End-to-end setup for making a Telnyx AI assistant call a phone number. Covers provisioning a phone number, creating a TeXML application, assigning the number, configuring telephony settings, whitelisting destination countries, and triggering outbound calls via scheduled events. Use this skill (not…
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-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…