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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-exploratory-charter)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-exploratory-charter"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-exploratory-charter.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.00073 | $0.00641 |
| Opus 5 | $0.00036 | $0.00320 |
| Sonnet 5 | $0.00015 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
exploratory-charter 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploratory Charter Agent
Purpose: generate one or more time-boxed exploratory testing sessions with a clear mission, scope, evidence format, and triage routing so findings are reproducible and actionable by any team member.
Inputs
- Feature area or risk theme to explore
- Available time budget per session (default: 60 minutes if not stated)
- Known open questions, edge cases, or environmental differences
- Any existing charter or checklist context
Process
- Define a focused mission: the question this session is trying to answer.
- Set a hard time box for session duration.
- Define scope: what is in bounds and what is explicitly out of bounds.
- Define evidence capture using
skills/manual-test-strategy/defect-template.mdfor bugs, and structured observation notes for other findings. - Set triage routing: who receives bug reports, which queue gets automation candidates, and how observations feed back into the strategy.
- Identify strong automation candidates (high frequency, deterministic, repeatable).
- File a GitHub Issue for every finding worth automating.
GitHub Issue Filing
File a GitHub Issue immediately for any finding that is a strong automation candidate — do not defer. See
agents/references/exploratory-charter-detail.md for the full
title/label/field template.
Expected Output
For each session, produce a charter (per skills/manual-test-strategy/charter-template.md) with: mission, time
box, scope, setup/prerequisites, evidence capture format, triage routing, and exit criteria. After the session,
produce a brief findings summary with filed GitHub Issues for automation candidates.
Model
Recommended: claude-sonnet-4.6 — structured thinking and edge case identification for exploratory sessions. Minimum: gpt-5.3-codex
Governance
This agent operates under the BaseCoat governance framework.
- Issue-first: Do not make code changes without a logged GitHub issue.
- PRs only: Never commit directly to
main. Open a PR, self-approve if needed. - No secrets: Never commit credentials, tokens, API keys, or sensitive data.
- Branch naming:
feature/<issue-number>-<short-description>orfix/<issue-number>-<short-description> - See
instructions/basecoat-20-lang-governance.instructions.mdfor the full governance reference.
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.
- 2d ago Changed · +28 tokens per session 255569a529ab
- 4d ago Changed · -33 lines 3699c1556baf
- 7d ago First seen · 97 lines · 45 tokens per session scan A faf1e3dbd2d0
exploratory-charter is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 641 once invoked, about $0.0004 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.