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.
npx skills add mtarcure/claude-vibe-squad --skill osint-platform-auditgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/skills/mtarcure/claude-vibe-squad/osint-platform-audit)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/osint-platform-audit"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/osint-platform-audit/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/skills/mtarcure/claude-vibe-squad/osint-platform-audit"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/osint-platform-audit.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.00077 | $0.00498 |
| Opus 5.5 | $0.00031 | $0.00199 |
| Sonnet 5.5 | $0.00015 | $0.00100 |
| Haiku 4.5 | $0.00008 | $0.00050 |
Grade A, and why
osint-platform-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 1mo 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSINT Platform Audit
Map an organization's externally-observable footprint from public sources only, and convert it into a defensible exposure inventory.
Steps
- Fix the authorization boundary before collecting anything: which domains, orgs, and identities are in scope, and confirm that collection is passive and permitted. Out-of-scope assets are not audited, only noted as adjacency.
- Enumerate the domain surface from public records — certificate transparency, passive DNS, WHOIS, and public subdomain sources — and record where each observation came from.
- Enumerate the code and artifact surface: public repositories, package registries, container registries, and published build artifacts belonging to the org.
- Enumerate the human surface only to the extent the audit requires: role pages, public profiles that establish who owns which system. Collect the minimum, and treat personal data as sensitive throughout.
- Search public leak and paste sources for org-linked credentials and tokens. Never authenticate with anything found; record existence and location only.
- Check public cloud surfaces for unintended exposure — open buckets, public snapshots, exposed dashboards — using read-only, unauthenticated checks.
- Correlate: link each observed asset to an owner, a purpose, and a confidence level. Unattributed assets are the most valuable output, because they are what the org does not know it has.
- Classify each exposure by what it enables, and separate "public by design" from "public by accident."
- Record collection dates and sources for everything; OSINT ages quickly and an undated finding cannot be re-verified.
Acceptance
- Scope and authorization are stated before any collection, and collection stayed passive.
- Every asset carries its source, observation date, and confidence.
- Assets are attributed to an owner and purpose, with unattributed ones called out.
- Discovered credentials were never used, only reported.
- Exposures are split into by-design and by-accident, with the enabled impact stated for each.
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.
- 1mo ago First seen · 28 lines · 77 tokens per session scan A a45f41d46aed
osint-platform-audit is a skill published in the GitHub repository mtarcure/claude-vibe-squad (165 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 498 once invoked, about $0.0003 per session on Opus 5.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-19.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
skill-installer
Install, update, trust, or inspect Codewhale skills from GitHub or local skill folders. Use when the user asks for available skills or wants a community skill installed.