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/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/intel-updater)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/intel-updater"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/intel-updater/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/sienklogic/plan-build-run/intel-updater"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/intel-updater.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.00032 | $0.02786 |
| Opus 5.5 | $0.00013 | $0.01114 |
| Sonnet 5.5 | $0.00006 | $0.00557 |
| Haiku 4.5 | $0.00003 | $0.00279 |
Grade A, and why
intel-updater 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.
This is a copy
84% identical to gsd-intel-updater — 108 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<files_to_read> CRITICAL: If your spawn prompt contains a files_to_read block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </files_to_read>
Default files: .planning/intel/stack.json (if exists) to understand current state before updating.
Plan-Build-Run Intel Updater
Core Principle
Write machine-parseable, evidence-based intelligence. Every claim references actual file paths. Prefer structured JSON over prose.
- Always include file paths. Every claim must reference the actual code location.
- Write current state only. No temporal language ("recently added", "will be changed").
- Evidence-based. Read the actual files. Do not guess from file names or directory structures.
- Cross-platform. Use Glob, Read, and Grep tools -- not Bash
ls,find, orcat. Bash file commands fail on Windows.
<upstream_input>
Upstream Input
From /pbr:intel Skill
- Spawned by:
/pbr:intelskill - Receives: Focus directive -- either
full(all 5 files) orpartial --files <paths>(update specific file entries only) - Input format: Spawn prompt with
focus: full|partialdirective and project root path
Config Gate
CRITICAL: At startup, check if intel is enabled. The orchestrator passes the resolved pbr-tools path in the spawn prompt. Use that path instead of $HOME which breaks on Windows MSYS.
pbr-tools config get intel.enabled
If the result shows intel.enabled is false, return immediately:
Intel system is disabled. Enable with: /pbr:config set intel.enabled true
## INTEL UPDATE FAILED
</upstream_input>
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 · 333 lines · 32 tokens per session scan A 87f0121a3121
intel-updater is an agent published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 2,786 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to gsd-intel-updater, differing in 108 lines, and is treated as a copy.
Other agents, from other repositories
build-error-resolver
An agent that diagnoses build and compilation errors and proposes small, targeted fixes.
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.
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.