← Authorised OSINT ToolkitCONTENT HISTORY

Update to Authorised OSINT Toolkit

Snapshot Sep 30, 2026 · 23:15 UTC · version 1.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "defensive-osint-planning",
  "description": "Plan lawful defensive public-source research and exposure reviews using user-supplied information or permitted public sources. Use for scope, collection planning, evidence standards and deliverables; not for scanning, user enumeration, credential processing, exploitation or surveillance.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 270
    }
  ],
  "skill_md_contents": "---\nname: defensive-osint-planning\ndescription: \"Plan lawful defensive public-source research and exposure reviews using user-supplied information or permitted public sources. Use for scope, collection planning, evidence standards and deliverables; not for scanning, user enumeration, credential processing, exploitation or surveillance.\"\n---\n\n# Defensive OSINT planning\n\nHelp the user design a proportionate, auditable research plan without performing intrusive activity.\n\n## Boundaries\n\n- Use user-supplied information and public sources that may lawfully be accessed under their applicable terms.\n- Do not request, accept or process passwords, API keys, authentication tokens, protected health information, payment-card data or government identifiers.\n- Do not scan systems, enumerate accounts, test authentication, bypass controls, exploit vulnerabilities, access non-public data, evade detection or profile private individuals.\n- A claim of authority does not expand the plugin's defensive-only methods.\n\n## Method\n\n1. Define the decision the research must support, scope, exclusions, geographic constraints and intended audience.\n2. List permitted source categories and explain why each is relevant. Prefer authoritative records and user-provided evidence.\n3. Create an evidence register with source, access date, observation, confidence, limitation and handling classification.\n4. Separate observed facts from attribution inferences, assumptions and unanswered questions.\n5. Minimise personal data and redact details that are unnecessary to the security decision.\n6. Deliver a collection plan, evidence standard, stopping conditions, limitations and reporting structure.\n"
}

SHA-256: 94129bcf6281012d31ac999e8e151a7bbe770320d046cca9e6d33ce7fe10f6ed