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 blisspixel/recon --skill recon-fingerprint-triagegit clone --depth 1 https://github.com/blisspixel/reconWrote 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/blisspixel/recon/recon-fingerprint-triage)<a href="https://agentmods.dev/skills/blisspixel/recon/recon-fingerprint-triage"><img src="https://agentmods.dev/badge/skills/blisspixel/recon/recon-fingerprint-triage/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/blisspixel/recon/recon-fingerprint-triage"><img src="https://agentmods.dev/badge/skills/blisspixel/recon/recon-fingerprint-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 29 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00080 | $0.02999 |
| Opus 5 | $0.00040 | $0.01499 |
| Sonnet 5 | $0.00016 | $0.00600 |
| Haiku 4.5 | $0.00008 | $0.00300 |
Grade A, and why
recon-fingerprint-triage 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 yesterday.
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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
recon-fingerprint-triage
This skill reviews the bounded public DNS observations that recon already collects and helps maintainers improve the fingerprint catalog. It supports the multi-record v2.14 quality loop rather than treating catalog growth as a count of new CNAME suffixes.
This is the portable Agent Skills form used by the schema-pinned
candidate. It omits client-only frontmatter and does not depend on experimental
allowed-tools behavior. Package compatibility remains unclaimed until the
frozen representative-client evaluation is complete.
When to use this
Use this skill when the user wants to:
- review unmatched DNS observations by record type;
- triage a private catalog baseline or recurrence queue;
- assess a proposed fingerprint rule;
- strengthen an existing slug with an independent evidence path;
- prepare a catalog patch and its required fixtures.
For an ordinary domain lookup, use the base recon skill. This skill is for
catalog maintenance, not general domain intelligence.
Environment and source checkout
An installed recon runtime or connected recon MCP server is enough to review
user-supplied observations and inspect the current catalog. Use the tool names
actually exposed by the client; no fixed MCP namespace or shell is required
when those tools are already connected. For catalog absence, read the complete
recon://fingerprints resource or page get_fingerprints(limit=20, offset=0)
until a page contains fewer than 20 entries. These catalog reads are local.
Catalog patching, formatter changes, validation scripts, and repository tests
require a separate recon source checkout selected by the user. Before using
them, identify that checkout root and read its AGENTS.md and project guidance.
Paths under docs/, src/, scripts/, validation/, and tests/ below refer
to that checkout, not the installed skill directory or an arbitrary working
directory. Documentation links may be read when browsing is available; they
do not provide executable scripts or a writable checkout.
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.
- yesterday Changed 302a54fe9347
- 4d ago Changed · +46 lines 8870d32f8467
- 7d ago Changed a922bdb75f09
- 11d ago First seen · 235 lines · 80 tokens per session scan A ccc16008cf05
recon-fingerprint-triage is a skill published in the GitHub repository blisspixel/recon (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 80 tokens to every session and 2,999 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-08-31.
Other skills, from other repositories
github-secret-hunting
Find leaked API keys, tokens, and credentials in public GitHub repositories.
google-dorks-catalog
High-precision Google dorks for exposed configs, secrets, and credentials -- real-world validated.
metabigor
Use when operating the metabigor CLI for OSINT recon and infrastructure mapping without API keys. Covers finding network ranges from an ASN, org, domain, or IP (net); enumerating subdomains from certificate logs (cert); enriching IPs with ports/CVEs via Shodan InternetDB (ip); searching public GitHub code for secrets…
osint-methodology
Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 5-stage recon pipeline (seed discovery, asset expansion, enrichment, exposure analysis, reporting), asset-graph discipline with 29 asset types, severity rubric (CRITICAL/HIGH/MEDIUM/LOW/INFO)…
conducting-external-reconnaissance-with-osint
Conducts external reconnaissance using Open Source Intelligence (OSINT) techniques to map an organization's external attack surface without directly interacting with target systems. The tester gathers information from public sources including DNS records, certificate transparency logs, search engines, social media…
offensive-osint
Operational arsenal for authorized external red-team and bug-bounty recon. Concrete probes, wordlists, regexes, dorks, curl one-liners for: subdomain enum, GraphQL/Swagger/REST discovery, identity fabric (Entra/Okta/ADFS/Google/SAML/M365 deep — Teams/SharePoint/OneDrive), cloud bucket enum (S3/GCS/Azure), CDN/WAF…