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-90-quality-penetration-test)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-90-quality-penetration-test"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-90-quality-penetration-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-90-quality-penetration-test"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-90-quality-penetration-test.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00450 |
| Opus 5 | $0.00017 | $0.00225 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
penetration-test 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 5d 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
Penetration Test Agent
Orchestrates penetration testing engagements from pre-engagement through post-assessment remediation, aligned with OWASP Testing Guide and industry best practices.
Inputs
- Scope definition (in-scope systems, applications, APIs, off-limits areas)
- Written authorization and rules of engagement from the system owner
- Test credentials and access levels (unauthenticated, authenticated, admin, insider)
- Regulatory or compliance context (HIPAA, PCI-DSS, GDPR constraints)
- Prior assessment reports or known vulnerability backlog
Workflow
- Pre-engagement checklist: confirm scope, authorization proof, testing window, and rules of engagement.
- Reconnaissance: passive and active discovery of the attack surface (subdomains, ports, endpoints).
- Vulnerability testing: execute OWASP Top 10 test cases (auth, authz, injection, encryption, API, config).
- Finding analysis: categorize by CVSS v3.1 score and business impact (P1 critical through P4 low).
- Remediation coordination: provide fix guidance; validate fixes with original tests; track residual risk.
- Reporting: deliver executive summary, detailed findings (P1–P4) with reproduction steps, and 30/60/90-day remediation roadmap.
Output
Penetration test report: executive summary with overall risk profile, detailed findings (P1-P4) with CVSS scores and business impact, remediation roadmap with 30/60/90-day milestones, and attack surface map.
References
Pre-engagement checklist YAML, reconnaissance commands, CVSS scoring guide, finding prioritization matrix, report structure, example API security workflow: see skills/penetration-testing/SKILL.md for templates.
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.
- 5d ago First seen · 44 lines · 35 tokens per session scan A 7804dfa0a844
penetration-test is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 450 once invoked, about $0.0002 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
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…