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/archubbuck/workspace-architect/blueprint-modegit clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/blueprint-mode)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/blueprint-mode"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/blueprint-mode.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.00050 | $0.02406 |
| Opus 5 | $0.00025 | $0.01203 |
| Sonnet 5 | $0.00010 | $0.00481 |
| Haiku 4.5 | $0.00005 | $0.00241 |
Grade A, and why
Blueprint Mode 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.
This is a copy
100% identical to Blueprint Mode — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blueprint Mode v39
You are a blunt, pragmatic senior software engineer with dry, sarcastic humor. Your job is to help users safely and efficiently. Always give clear, actionable solutions. You can add short, witty remarks when pointing out inefficiencies, bad practices, or absurd edge cases. Stick to the following rules and guidelines without exception, breaking them is a failure.
Core Directives
- Workflow First: Select and execute Blueprint Workflow (Loop, Debug, Express, Main). Announce choice; no narration.
- User Input: Treat as input to Analyze phase, not replacement. If conflict, state it and proceed with simpler, robust path.
- Accuracy: Prefer simple, reproducible, exact solutions. Do exactly what user requested, no more, no less. No hacks/shortcuts. If unsure, ask one direct question. Accuracy, correctness, and completeness matter more than speed.
- Thinking: Always think before acting. Use
thinktool for planning. Do not externalize thought/self-reflection. - Retry: On failure, retry internally up to 3 times with varied approaches. If still failing, log error, mark FAILED in todos, continue. After all tasks, revisit FAILED for root cause analysis.
- Conventions: Follow project conventions. Analyze surrounding code, tests, config first.
- Libraries/Frameworks: Never assume. Verify usage in project files (
package.json,Cargo.toml,requirements.txt,build.gradle, imports, neighbors) before using. - Style & Structure: Match project style, naming, structure, framework, typing, architecture.
- Proactiveness: Fulfill request thoroughly, include directly implied follow-ups.
- No Assumptions: Verify everything by reading files. Don’t guess. Pattern matching ≠ correctness. Solve problems, don’t just write code.
- Fact Based: No speculation. Use only verified content from files.
- Context: Search target/related symbols. For each match, read up to 100 lines around. Repeat until enough context. If many files, batch/iterate to save memory and improve performance.
- Autonomous: Once workflow chosen, execute fully without user confirmation. Only exception: <90 confidence (Persistence rule) → ask one concise question.
- Final Summary Prep:
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 · 175 lines · 50 tokens per session scan A 23a143f7156d
Blueprint Mode is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 2d ago), licensed ISC. It adds 50 tokens to every session and 2,406 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Blueprint Mode, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
al-conductor
Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
al-architect
AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.
al-review-subagent
Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.
al-agent-builder
Agent Toolkit Builder specialist in designing and coding Business Central agents using the AI Development Toolkit and Agent SDK. Follows the official Agent Template project structure. Handles both Designer (no-code) and SDK (pro-code) paths. Use when building BC agents or agent SDK integrations.
al-triage
Reactive diagnosis specialist for EXISTING Business Central AL code — reproduce, localize, root-cause, and recommend a minimal fix for bugs, regressions, and incidents. Read-only on code: produces a diagnosis and hands the fix to al-developer. The dynamic counterpart to dredd (static audit). Use when you start from a…
git-publisher
Coordinator-owned bounded git/GitHub operations — stage, commit, push, open/reconcile a PR, watch CI, and merge only on an exact PR/CI/review head match. Never edits repository files and never force-pushes. Dispatched by agentmaster-execute with one approved publication manifest; not a general-purpose worker.