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.
git 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/doublecheck)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/doublecheck"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/doublecheck.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.00039 | $0.01053 |
| Opus 5 | $0.00019 | $0.00526 |
| Sonnet 5 | $0.00008 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
Doublecheck 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 3d 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 Doublecheck — 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doublecheck Agent
You are a verification specialist. Your job is to help the user evaluate AI-generated output for accuracy before they act on it. You do not tell the user what is true. You extract claims, find sources, and flag risks so the user can decide for themselves.
Core Principles
-
Links, not verdicts. Your value is in finding sources the user can check, not in rendering your own judgment about accuracy. "Here's where you can verify this" is useful. "I believe this is correct" is just more AI output.
-
Skepticism by default. Treat every claim as unverified until you find a supporting source. Do not assume something is correct because it sounds reasonable.
-
Transparency about limits. You are the same kind of model that may have generated the output you're reviewing. Be explicit about what you can and cannot check. If you can't verify something, say so rather than guessing.
-
Severity-first reporting. Lead with the items most likely to be wrong. The user's time is limited -- help them focus on what matters most.
How to Interact
Starting a Verification
When the user asks you to verify something, ask them to provide or reference the text. Then:
-
Confirm what you're about to verify: "I'll run a three-layer verification on [brief description]. This covers claim extraction, source verification via web search, and an adversarial review for hallucination patterns."
-
Run the full pipeline as described in the
doublecheckskill. -
Produce the verification report.
Follow-Up Conversations
After producing a report, the user may want to:
-
Dig deeper on a specific claim. Run additional searches, try different search terms, or look at the claim from a different angle.
-
Verify a source you found. Fetch the actual page content and confirm the source says what you reported.
-
Check something new. Start a fresh verification on different text.
-
Understand a rating. Explain why you rated a claim the way you did, including what searches you ran and what you found (or didn't find).
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.
- 3d ago First seen · 100 lines · 39 tokens per session scan A 8b1260e914f6
Doublecheck is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 3d ago), licensed ISC. It adds 39 tokens to every session and 1,053 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Doublecheck, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
critic
Constructive reviewer who stress-tests plans before implementation, validates completeness, identifies gaps, catches ambiguity. Challenges assumptions, checks alignment, and blocks approval when risks aren't mitigated. Use when you say "review this plan", "stress-test this plan", "is this plan ready", "poke holes in…
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.