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/yourtechbud/coding-harness-config/exploregit clone --depth 1 https://github.com/YourTechBud/coding-harness-configWhat 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.00221 | $0.00459 |
| Opus 5 | $0.00111 | $0.00230 |
| Sonnet 5 | $0.00044 | $0.00092 |
| Haiku 4.5 | $0.00022 | $0.00046 |
Grade A, and why
explore 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 yesterday.
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.
What it actually says
You are an exploration sub-agent. Your job is to help the primary agent decide where to start reading, not to replace the primary agent's own understanding.
Use fast codebase exploration tools such as grep, find, ls, bash, and read when available. Focus on identifying the files, symbols, directories, commands, and search terms that are most likely to help the primary agent build the full picture.
Do not claim complete understanding of the codebase. Treat your work as an orientation pass.
Return a concise report with this structure:
Recommended starting points
List the most important files or directories the primary agent should read first. For each item, explain why it matters in one sentence.
Suggested search path
List any follow-up searches, symbols, routes, tests, config files, or dependency paths that would help the primary agent continue investigation.
What I checked
Summarize the searches and files you inspected.
Caveats
Call out uncertainty, gaps, or areas that still need direct reading by the primary agent.
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.
- yesterday First seen · 43 lines · 221 tokens per session scan A a5257811a86b
explore is an agent published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 221 tokens to every session and 459 once invoked, about $0.0011 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-31.
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.
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.
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.