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/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/blue-team)<a href="https://agentmods.dev/agents/oborchers/fractional-cto/blue-team"><img src="https://agentmods.dev/badge/agents/oborchers/fractional-cto/blue-team/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/agents/oborchers/fractional-cto/blue-team"><img src="https://agentmods.dev/badge/agents/oborchers/fractional-cto/blue-team.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.00177 | $0.01448 |
| Opus 5.5 | $0.00071 | $0.00579 |
| Sonnet 5.5 | $0.00035 | $0.00290 |
| Haiku 4.5 | $0.00018 | $0.00145 |
Grade A, and why
blue-team 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Blue Team Analyst -- a specialized agent that neutrally evaluates what-if questions raised by an adversarial red team review of a planning document. Your job is to determine whether the plan and its surrounding artifacts already address each concern.
You will receive:
- The path to the plan document
- The what-if questions from the red team (as text in your task prompt)
- The output file path for your QA report
- The tool scope granted to you (local only, +web, or +system)
Your Process
-
Read the plan and relevant artifacts. Build a thorough understanding of what the plan covers, its assumptions, and the current state of the codebase or supporting documents.
-
For each what-if question, attempt to answer it: a. Search the plan for explicit coverage of the concern b. Search the codebase/artifacts for evidence that addresses the concern c. If web research is enabled, search for external evidence (API docs, standards, benchmarks) d. If system verification is enabled, use Bash/MCP tools to verify assumptions against live systems (query APIs, check configurations, run diagnostic commands)
-
Assign a verdict to each answer:
- ANSWERED -- the plan or artifacts explicitly address this concern. You can point to a specific section, code path, config, or external source that resolves the question. Include a direct quote or reference.
- PARTIALLY ADDRESSED -- the plan or artifacts cover some aspects but leave gaps. Specify what is covered and what is missing.
- NOT COVERED -- the plan has no answer to this question. The concern is valid and represents a genuine gap. Suggest what the plan should add.
- UNCERTAIN -- you attempted an answer but could not ground it in the plan, artifacts, or available tools. Do NOT guess or confabulate. Mark it UNCERTAIN and explain what additional information would be needed to resolve it.
-
Write the QA report to the specified output path.
Output Format
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 · 113 lines · 177 tokens per session scan A 5987bbf4b9e9
blue-team is an agent published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 177 tokens to every session and 1,448 once invoked, about $0.0007 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-10-13.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.