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 Miosa-osa/OSA --skill offensive-osint-methodologygit clone --depth 1 https://github.com/Miosa-osa/OSAWrote 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/miosa-osa/osa/offensive-osint-methodology)<a href="https://agentmods.dev/skills/miosa-osa/osa/offensive-osint-methodology"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/offensive-osint-methodology/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/miosa-osa/osa/offensive-osint-methodology"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/offensive-osint-methodology.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.00044 | $0.05765 |
| Opus 5.5 | $0.00018 | $0.02306 |
| Sonnet 5.5 | $0.00009 | $0.01153 |
| Haiku 4.5 | $0.00004 | $0.00577 |
Grade A, and why
offensive-osint-methodology 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.
This is a copy
95% identical to offensive-osint-methodology — 53 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: OSINT Methodology
Metadata
- Skill Name: osint-methodology
- Folder: offensive-osint-methodology
- Source: https://github.com/SnailSploit/offensive-checklist/blob/main/osint-method.md
Description
Structured OSINT methodology framework: target definition, source selection, collection workflows, data correlation, timeline reconstruction, and reporting. Use to guide systematic OSINT campaigns or teach OSINT methodology.
Trigger Phrases
Use this skill when the conversation involves any of:
OSINT methodology, open source intelligence, target profiling, data correlation, OSINT workflow, intelligence collection, OSINT campaign, recon methodology
Full Methodology
OSINT Methodology
OpSec
Create a Sock Puppet
- Fake account that cannot be linked to you
- Build a posting history (post stuff, etc.)
- Resources
- Effective Sock Puppets
- Ultimate Guide to Sock Puppets
- Fake Name Generator
- This Person does not Exist
- Use separate browser profiles or isolation tools (e.g., Firefox Multi‑Account Containers) for any sock‑puppet activity.
- Acquire disposable VoIP/SMS numbers (e.g., Burner, Silent Link) to satisfy platform verification without exposing real phone numbers.
- Audit every browser extension before installation; supply‑chain attacks on popular add‑ons have targeted investigators since 2024.
- Use dedicated browser profiles/containers per case and persona; avoid logging into personal accounts.
- Prefer hardware‑backed passkeys for critical accounts; store recovery codes offline.
- Maintain a minimal chain‑of‑custody: timestamp actions, hash key artifacts, and record tool versions per case.
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 · 466 lines · 44 tokens per session scan A 68f6f51107d4
offensive-osint-methodology is a skill published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 11d ago), licensed Apache-2.0. It adds 44 tokens to every session and 5,765 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to offensive-osint-methodology, differing in 53 lines, and is treated as a copy.
Other skills, from other repositories
unit-converter
Converts between common units of measurement including temperature, distance, and weight.
code-review
Reviews code changes for quality, security, and best practices.
tui-design
This skill should be used when designing terminal user interfaces, creating TUI layouts, choosing TUI color schemes, implementing keyboard navigation, building terminal dashboards, or working with any TUI framework. Activates on mentions of TUI design, terminal UI, Ratatui layout, Ink components, Textual widgets…
bun-development
Fast, modern JavaScript/TypeScript development with the Bun runtime, inspired by oven-sh/bun.
worker-mcp-orchestrator
Guides the coordinator agent on how to orchestrate, delegate to, and supervise local worker agents using the worker-mcp server.
clack
Build and maintain interactive Node.js/Bun CLIs with Clack (@clack/prompts and @clack/core). Use when an AI agent needs to design prompt flows, implement cancellation-safe input handling, add spinners/log/note UX, apply Clack best practices, or generate runnable examples aligned with official Clack docs.