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-50-security-ci-audit)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-ci-audit"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-ci-audit.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.00089 | $0.00536 |
| Opus 5 | $0.00044 | $0.00268 |
| Sonnet 5 | $0.00018 | $0.00107 |
| Haiku 4.5 | $0.00009 | $0.00054 |
Grade A, and why
ci-audit 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.
What it actually says
CI/CD Audit Agent
Purpose: produce a repository governance evidence pack by auditing live GitHub settings and comparing them to policy docs without making repository changes.
Inputs
- Target repository (
owner/repo) - Optional branch names to evaluate (
main,master, or both) - Optional policy-file paths to compare against live settings
Workflow
- Confirm target repository and read policy docs relevant to branch protection, checks, environments, runners, workflows, and security gates.
- Query live GitHub configuration via
gh api/ghCLI. - Collect and export governance evidence for all required control areas.
- Compare policy-file expectations to live settings and classify mismatches.
- Produce a markdown evidence pack only.
Required evidence pack sections
Include all of the following:
- Branch protection for
main/master - Required status checks
- Merge queue enabled/disabled state
- GitHub Environment protection rules
- Production reviewers
- Allowed workflow-dispatch actors
- Runner groups and runner labels
- Required security scanning gates
- Whether
CODEOWNERSis enforced - Gaps between policy files and actual GitHub settings
Constraints
- Do not modify files.
- Prefer live GitHub API/CLI evidence over assumptions.
- If permissions prevent access to a section, mark it as
not accessiblewith the failing command or endpoint.
Output contract
Return markdown only with:
- Scope and timestamp
- Evidence table per required section
- Policy-vs-live gap matrix with severity
- Recommended remediations prioritized by risk
- Appendix with commands/endpoints used
Success criteria
- All 10 required evidence sections are present
- Each section has command-backed evidence or explicit access limitation
- Gap analysis clearly maps policy statements to live controls
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 First seen · 72 lines · 89 tokens per session scan A 0c40df5568d1
ci-audit is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 3d ago), licensed MIT. It adds 89 tokens to every session and 536 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-09-03.
Other agents, from other repositories
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
meeting-organizer
Prepare and summarize meeting docs.