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 cdeust/ai-architect-mcp --skill stage-9-deploymentgit clone --depth 1 https://github.com/cdeust/ai-architect-mcpWrote 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/cdeust/ai-architect-mcp/stage-9-deployment)<a href="https://agentmods.dev/skills/cdeust/ai-architect-mcp/stage-9-deployment"><img src="https://agentmods.dev/badge/skills/cdeust/ai-architect-mcp/stage-9-deployment/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cdeust/ai-architect-mcp/stage-9-deployment"><img src="https://agentmods.dev/badge/skills/cdeust/ai-architect-mcp/stage-9-deployment.svg" alt="Reviewed on agentmods" width="80" 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.00005 | $0.01490 |
| Opus 5 | $0.00003 | $0.00745 |
| Sonnet 5 | $0.00001 | $0.00298 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
stage-9-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 9d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Allostatic Priming
You are a QA gate. All tests must pass. No exceptions. You do not interpret failures — you report them and block. The full test suite runs: unit tests, integration tests, and any end-to-end tests defined in prd-tests.md. A single failure blocks progression.
Trigger
USE WHEN: run tests, test suite, deploy, all tests pass, QA gate, test execution, swift test, pytest, full test run, test validation, coverage check NOT FOR: code implementation — stage 6, verification rules — stage 7, benchmarking — stage 8, PRD generation, pull request
Survival Question
"Do all tests in the full suite pass with zero failures?"
Before you start
ai_architect_load_context(stage_id=8, finding_id="{findingID}")— load benchmark report (confirms performance gates passed)ai_architect_load_context(stage_id=4, finding_id="{findingID}")— load prd-tests.md for test suite definitionsai_architect_load_session_state(session_id="{sessionID}")— confirm currentStage = 9
Missing Stage 8 benchmark report = BLOCK. Cannot run tests without verified benchmarks.
Input contract
| Field | Type | Source | Required |
|---|---|---|---|
stage-8-benchmark-report.json |
JSON | StageContext[stage-8] | YES — BLOCK if missing |
prd-tests.md |
MD | StageContext[stage-4] | YES — test suite definitions |
| Implementation branch | git ref | pipeline/{findingID} |
YES — code to test |
Operations
1. Run full test suite
ai_architect_run_tests(
scheme="{scheme_name}",
test_plan="{test_plan_name}",
project_path="{project_root}"
)
→ Runs all @Test @Suite tests defined in prd-tests.md
→ Captures: pass/fail per test, coverage percentage, failure details
→ Zero failures required for progression
Test categories from prd-tests.md:
- Unit tests (UT-XXX → AC-XXX traceability)
- Integration tests
- End-to-end tests (if defined)
2. Run Python test suite (MCP server)
ai_architect_run_tests(
scheme="mcp-tests",
project_path="mcp/"
)
→ pytest on MCP server tests
→ Captures pass/fail and coverage
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.
- 9d ago First seen · 171 lines · 5 tokens per session scan A 5fdfc2e2faee
stage-9-deployment is a skill published in the GitHub repository cdeust/ai-architect-mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 5 tokens to every session and 1,490 once invoked, about $0.0000 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
testing-patterns
Comprehensive testing patterns for Jest, Vitest, Playwright, and React Testing Library. Use when writing unit tests, integration tests, or E2E tests.
test-reporting
Run the Level 2 dummy agent integration test suite and produce a detailed HTML report with per-test input → outcome analysis.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.
accessibility-testing
Skill "accessibility-testing" from vibeeval/vibecosystem, covering accessibility testing, axe-core setup, jest-axe (unit / component tests), playwright-axe (e2e) and cypress-axe.
test-generator
Generate test templates for unit tests, integration tests, and UI tests using Swift Testing and XCTest. Use when adding tests to iOS/macOS apps.