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-bddgit 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-bdd)<a href="https://agentmods.dev/skills/syntaxarc/archipy-plugin/scaffold-archipy-bdd"><img src="https://agentmods.dev/badge/skills/syntaxarc/archipy-plugin/scaffold-archipy-bdd.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.00046 | $0.00766 |
| Opus 5 | $0.00023 | $0.00383 |
| Sonnet 5 | $0.00009 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
scaffold-archipy-bdd 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold ArchiPy BDD
Before writing files
Ask the user for:
- Feature name / file stem (e.g.
user_registration) - Mode: mocks only vs infra (
@needs-*+ testcontainers)
Prefer ArchiPy
uv add "archipy[behave]"
# infra mode also:
uv add "archipy[testcontainers]"
Generate
Under project root (create shared files only if missing):
features/
├── <name>.feature
├── steps/
│ └── <name>_steps.py
├── scenario_context.py # always — adapt from ArchiPy pattern
├── scenario_context_pool_manager.py # always — Singleton pool
├── environment.py # always — behave hooks
├── test_helpers.py # always — get_current_scenario_context
└── test_containers.py # infra mode only — ContainerManager + needed containers
.env.test # infra mode — REDIS__IMAGE, POSTGRES__IMAGE, …
Model after ArchiPy features/ + docs tutorial (consumer-slim — no library gRPC/Temporal special cases unless the app
needs them).
Copy templates from reference/, adapt package imports, create only if missing:
| Destination | Template |
|---|---|
features/scenario_context.py |
reference/scenario_context.py |
features/scenario_context_pool_manager.py |
reference/scenario_context_pool_manager.py |
features/test_helpers.py |
reference/test_helpers.py |
features/environment.py |
reference/environment.py |
Uncomment / wire ContainerManager in environment.py when mode is infra.
features/test_containers.py (infra mode)
Copy pattern from ArchiPy features/test_containers.py, not the full multi-service registry:
TAG_CONTAINER_MAP(needs-redis→redis, …)ContainerManagerwithregister,get_container,start_containers,extract_containers_from_tags,stop_all- Only register containers the app actually tests (e.g. one
RedisTestContainerSingleton that startsRedisContainer, patchesBaseConfig.global_config().REDIS)
What ships with it
4 files 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.
- 7d ago First seen · 86 lines · 46 tokens per session scan A 63b3fb17c785
scaffold-archipy-bdd is a skill published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed 14d ago), licensed MIT. It adds 46 tokens to every session and 766 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
bdd-methodology
Use when writing, reviewing, or structuring BDD scenarios in Gherkin format. Covers Given/When/Then conventions, scenario outline patterns, background usage, tag strategies, and domain language alignment. Load before any Gherkin authoring.
playwright-evidence
Use when capturing E2E test evidence (screenshots, videos, traces) and storing them in .copilot-tracking/skraft-plans/{projectSlug}/changes/{date}/evidence/{story}/evidence/ for agents to consume. Covers Playwright setup, on-failure capture, trace collection, and evidence manifest generation.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.