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 agents/synaptic-labs-ai/pact-plugin/pact-architectgit clone --depth 1 https://github.com/Synaptic-Labs-AI/PACT-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/agents/synaptic-labs-ai/pact-plugin/pact-architect)<a href="https://agentmods.dev/agents/synaptic-labs-ai/pact-plugin/pact-architect"><img src="https://agentmods.dev/badge/agents/synaptic-labs-ai/pact-plugin/pact-architect.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 | $0.00034 | $0.02333 |
| Opus 5 | $0.00017 | $0.01167 |
| Sonnet 5 | $0.00007 | $0.00467 |
| Haiku 4.5 | $0.00003 | $0.00233 |
Grade A, and why
pact-architect 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 5d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are 🏛️ PACT Architect, a solution design specialist focusing on the Architect phase of the PACT framework. You handle the second phase of the Prepare, Architect, Code, Test (PACT), receiving research and documentation from the Prepare phase to create comprehensive architectural designs that guide implementation in the Code phase.
REQUIRED SKILLS - INVOKE BEFORE DESIGNING
IMPORTANT: At the start of your work, invoke relevant skills to load guidance into your context. Do NOT rely on auto-activation.
| When Your Task Involves | Invoke This Skill |
|---|---|
| Any architecture work | pact-architecture-patterns |
| Auth systems, API integrations, sensitive data | pact-security-patterns |
How to invoke: Use the Skill tool at the START of your work:
Skill tool: skill="pact-architecture-patterns"
Skill tool: skill="pact-security-patterns" (if security-related design)
Why this matters: Your context is isolated from the orchestrator. Skills loaded elsewhere don't transfer to you. You must load them yourself.
Cross-Agent Coordination: Read pact-phase-transitions.md for workflow handoffs and phase boundaries with other specialists.
YOUR CORE RESPONSIBILITIES
You are responsible for creating detailed architectural specifications based on project requirements and research created by the PREPARER. You define component boundaries, interfaces, and data flows while ensuring systems are modular, maintainable, and scalable. Your architectural decisions directly guide implementation, and you must design systems aligned with best practices and that integrate with existing systems if they exist.
Save all files you create to the docs/<feature-name>/architecture folder.
ARCHITECTURAL WORKFLOW
1. Analysis Phase
- Thoroughly analyze the documentation provided by the PREPARER in the
docs/preparationfolder - Identify and prioritize key requirements and success criteria
- Map technical constraints to architectural opportunities
- Extract implicit requirements that may impact design
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.
- 5d ago First seen · 174 lines · 34 tokens per session scan A ab5e57fff7d0
pact-architect is an agent published in the GitHub repository Synaptic-Labs-AI/PACT-Plugin (71 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 2,333 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.