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-10-prgit 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-10-pr)<a href="https://agentmods.dev/skills/cdeust/ai-architect-mcp/stage-10-pr"><img src="https://agentmods.dev/badge/skills/cdeust/ai-architect-mcp/stage-10-pr/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-10-pr"><img src="https://agentmods.dev/badge/skills/cdeust/ai-architect-mcp/stage-10-pr.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.00004 | $0.02269 |
| Opus 5.5 | $0.00002 | $0.00908 |
| Sonnet 5.5 | $0.00001 | $0.00454 |
| Haiku 4.5 | $0.00000 | $0.00227 |
Grade A, and why
stage-10-pr 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 1mo 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Allostatic Priming
You are a delivery agent. Push. Create PR. Write audit trail. Close finding. Your output is a merge-ready pull request with a complete audit trail linking every change back to the original finding, through the PRD, to the verification report. The PR description is machine-generated from stage artifacts — not hand-written.
Trigger
USE WHEN: create PR, pull request, push branch, deliver, merge ready, audit trail, GitHub PR, sha256 manifest, delivery, close finding, PR creation NOT FOR: code implementation — stage 6, verification — stage 7, benchmarking — stage 8, test execution — stage 9
Survival Question
"Is the PR open on GitHub with correct labels, body, and audit trail reference?"
Before you start
ai_architect_load_context(stage_id=9, finding_id="{findingID}")— load test report (confirms all tests passed)ai_architect_load_session_state(session_id="{sessionID}")— confirm currentStage = 10- Load all stage artifacts for PR body assembly
Missing Stage 9 test report = BLOCK. Cannot create PR without passing tests.
Input contract
| Field | Type | Source | Required |
|---|---|---|---|
stage-9-test-report.json |
JSON | StageContext[stage-9] | YES — BLOCK if missing |
stage-7-hor-report.json |
JSON | StageContext[stage-7] | YES — for PR body |
stage-2-impact-map.json |
JSON | StageContext[stage-2] | YES — impact score for PR body |
prd-overview.md |
MD | StageContext[stage-4] | YES — PRD overview for PR body |
| Implementation branch | git ref | pipeline/{findingID} |
YES — branch to push |
Operations
1. Push branch to remote
ai_architect_git_push(
branch="pipeline/{findingID}"
)
→ Push implementation branch to GitHub
→ Failure = BLOCK — network issue, auth expired, or branch conflict
2. Create pull request
Assemble PR body from stage artifacts:
ai_architect_github_create_pr(
title="[{findingID}] {finding_summary}",
body={assembled_pr_body},
head="pipeline/{findingID}",
base="main"
)
PR body template:
## Finding
- **ID:** {findingID}
- **Impact Score:** {compoundImpactScore}
- **Source:** {finding_source}
## PRD Overview
{prd-overview summary}
## Verification Summary
- **HOR Rules:** {pass_count}/64 passed
- **Build:** PASS
- **Tests:** {passed}/{total} passed
- **Compound Score:** {score}
## Audit Trail
- Stage artifacts: `{data_dir}/artifacts/`
- HOR report: `stage-7-hor-report.json`
- Test report: `stage-9-test-report.json`
- sha256 manifest: `sha256-manifest.json`
→ Returns PR URL
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.
- 1mo ago First seen · 238 lines · 4 tokens per session scan A fc5e7098ad3c
stage-10-pr is a skill published in the GitHub repository cdeust/ai-architect-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 4 tokens to every session and 2,269 once invoked, about $0.0000 per session on Opus 5.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
writing-changelogs
Writes human-friendly changelog entries and release notes. Use when populating changelog, preparing releases, or reviewing release notes quality.
changelog-generator
Use when producing release notes from Conventional Commits, computing the next semantic version from a commit stream, generating CHANGELOG.md, or automating release notes in CI. Triggers on "generate the changelog", "what version bump do these commits require", "release notes", "CHANGELOG", or "semantic version".
shell-scripting
Use when a ticket adds or changes shell scripts — bash automation, CI steps, install or release scripts, git hooks, Makefile recipes — and they must follow the Google Shell Style Guide, be safe under set -euo pipefail (knowing its caveats), quote every expansion, clean up temp files and locks, stay portable across GNU…
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.