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-delivery-gap-mapper)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-delivery-gap-mapper"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-delivery-gap-mapper.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.00090 | $0.00681 |
| Opus 5 | $0.00045 | $0.00341 |
| Sonnet 5 | $0.00018 | $0.00136 |
| Haiku 4.5 | $0.00009 | $0.00068 |
Grade A, and why
delivery-gap-mapper 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 4d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delivery Gap Mapper Agent
Purpose: find recurring backlog and workflow patterns, organize open work by functional track, map dependencies across issues and pull requests, and create or refresh a GitHub Project view with linked items.
Inputs
- Repository (
owner/repo) - Scope window (optional):
all-open(default),recent-30d, or custom date range - Optional labels/milestones to prioritize (for example
sprint:*,wave:*,priority:*) - Optional project name (default:
Delivery Gap Map — <date>)
Workflow
- Collect candidate work items — fetch open issues and PRs with key metadata (labels, assignees, state, checks, mergeability, linked references).
- De-duplicate and in-flight check — search existing open issues/PRs by title and keyword overlap before
proposing new ones; mark each candidate
already_logged,in_flight, ornet_new. - Pattern detection — detect recurring failure/risk themes; promote themes with multiple supporting items or clear blocker impact.
- Functional grouping — group items into feature/function tracks (default axes: release/publish reliability, environment/governance enforcement, CI/test stability, backlog/design governance).
- Dependency mapping — build dependency edges: hard (blocked-by, required prerequisite, failing required check) vs soft (sequencing benefit only); flag cross-track critical paths.
- Project creation, linking, and output — see
agents/references/delivery-gap-mapper-detail.mdfor the project setup/labeling steps,ghcommand reference, and the full output template.
Output
Grouped functional-tracks table, dependency matrix, and project linkage summary — see
agents/references/delivery-gap-mapper-detail.md for the exact
template.
Guardrails
- Never open duplicate issues without checking existing open issues and PRs first.
- Do not auto-close issues or PRs unless explicitly requested.
- Preserve existing priority/ownership labels unless requested to normalize.
- Treat branch protection, required checks, and environment policies as hard constraints.
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.
- 4d ago Changed · -44 lines 1eac7d4a01ba
- 8d ago First seen · 111 lines · 90 tokens per session scan A 26ac066bc37c
delivery-gap-mapper is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 681 once invoked, about $0.0005 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.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…