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.
/plugin marketplace add blisspixel/reconnpx agentmods add plugins/blisspixel/recon/claude-codegit clone --depth 1 https://github.com/blisspixel/reconGrade A, and why
recon 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.
What it actually says
{
"name": "recon",
"version": "2.18.0",
"description": "Public-metadata domain intelligence for Microsoft 365 / Google Workspace tenant identification, email security observation (DMARC, DKIM, SPF, MTA-STS, BIMI), SaaS fingerprinting, certificate-transparency findings, and posture analysis. Bundles the recon MCP server and its usage guidance.",
"author": {
"name": "blisspixel",
"url": "https://github.com/blisspixel"
},
"homepage": "https://github.com/blisspixel/recon",
"repository": "https://github.com/blisspixel/recon",
"license": "Apache-2.0",
"keywords": [
"recon",
"osint",
"dns",
"passive-recon",
"m365",
"google-workspace",
"dmarc",
"saas-fingerprinting"
]
}
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 First seen · 23 lines scan A 38e601591395
recon is a plugin published in the GitHub repository blisspixel/recon (4 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
osint-deploy
Install, run and verify OSINT tools from GitHub on macOS, Windows or Linux.
osint-deploy-marketplace
Deploy-and-verify tooling for OSINT tools from GitHub.
dns-doctor
Diagnose and fix a domain's email authentication (SPF, DMARC, DKIM, MX, blacklist, expiry). Returns deterministic verdicts and copy-paste fix records generated by a validating engine — never a guessed record.
spotlight-plugin
Plugin marketplace listing 1 plugin: spotlight.
spotlight
OSINT investigation orchestration for journalists: structured briefs, methodology approval, sourced findings, independent fact-checking, review artifacts, and knowledge ingestion.
magpie
FOSS-first investigative analysis toolkit. Turn FOIA releases and data dumps into findings you can stand behind: counted, cited to the exact page, swept for PII, and filed as linked notes, all locally in your own Claude Code session. Covers structured-data analysis, document ingest, redaction checks, and opt-in entity.