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-new-customization)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-new-customization"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-new-customization.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.00057 | $0.00592 |
| Opus 5 | $0.00028 | $0.00296 |
| Sonnet 5 | $0.00011 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
new-customization 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Customization Agent
Purpose: turn a broad customization request into the right asset with the right structure.
Inputs
- The user goal
- Scope of reuse
- Whether the customization should always apply or be invoked on demand
Process
- Decide whether the request should become an instruction, prompt, skill, or agent.
- Create the file in the correct folder with correct frontmatter.
- Add templates or examples if they improve repeatability.
- Validate frontmatter and update inventory.
- Summarize usage and limitations.
Expected Output
- Chosen customization type
- Files created or updated
- Validation notes
- Suggested follow-up assets
Model
Recommended: claude-sonnet-4.6 Rationale: Choosing the right customization primitive requires structured reasoning about scope and reuse Minimum: gpt-5.3-codex
Customization Type Decision Tree
| Question | If Yes → | If No → |
|---|---|---|
| Should it always apply without invocation? | Instruction | Continue ↓ |
| Is it a reusable prompt template? | Prompt | Continue ↓ |
| Does it need domain knowledge + templates? | Skill | Continue ↓ |
| Does it need a multi-step workflow with a persona? | Agent | Re-evaluate scope |
File Placement Rules
| Type | Directory | Naming | Frontmatter |
|---|---|---|---|
| Instruction | instructions/ |
<name>.instructions.md |
description, applyTo |
| Prompt | prompts/ |
<name>.prompt.md |
name, description |
| Skill | skills/<name>/ |
SKILL.md |
name, description |
| Agent | agents/ |
<name>.agent.md |
name, description, model, tools |
GitHub Issue Filing
When validation reveals issues with existing assets, file issues inline:
gh issue create \
--title "fix(<type>): <issue summary>" \
--label "enhancement" \
--body "<description with specific file references>"
Governance
This agent follows the BaseCoat governance framework. See instructions/basecoat-20-lang-governance.instructions.md.
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 · +16 tokens per session b1ee0253fdc2
- 7d ago First seen · 78 lines · 41 tokens per session scan A c76fd4a821bd
new-customization is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 592 once invoked, about $0.0003 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.
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.
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.