horizon-scanning

horizon-scanning is a skill for Claude Code from Liberty91LTD/cti-skills. It costs 44 tokens per session (823 once invoked), scanned A, original, MIT.

A method for looking for early signs of future threats, opportunities, and technology changes over roughly six to 24 months. It uses sources such as research, security conferences, regulations, patents, and technology trends.

In plain words
What is it for?
Use it to define a forecasting area, collect weak signals, group emerging risks, and develop possible future scenarios.
Why use it?
It helps organisations notice developments before they become immediate security or business problems.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to define a forecasting area, collect weak signals, group emerging risks, and develop possible future scenarios.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/liberty91ltd/cti-skills/horizon-scanning
Install

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.

Any agent
npx skills add Liberty91LTD/cti-skills --skill horizon-scanning
Clone the repo
git clone --depth 1 https://github.com/Liberty91LTD/cti-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for horizon-scanning

README.md
[![agentmods](https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/horizon-scanning/github.svg)](https://agentmods.dev/skills/liberty91ltd/cti-skills/horizon-scanning)
Your own site
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/horizon-scanning"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/horizon-scanning/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.

agentmods 80×15 button for horizon-scanning

Your own site · 80×15
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/horizon-scanning"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/horizon-scanning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 823 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00823
Opus 5 $0.00022 $0.00411
Sonnet 5 $0.00009 $0.00165
Haiku 4.5 $0.00004 $0.00082

Measured 12d ago against content hash d6d4a938d87d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

horizon-scanning 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 12d 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.

skills/horizon-scanning/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Horizon Scanning

Horizon scanning identifies emerging threats, opportunities, and developments that could impact the organisation's security posture in the medium to long term (6-24 months).

Process

1. Define Scope

  • Time horizon (6 months? 12 months? 24 months?)
  • Focus areas (specific sectors, threat types, geographies)
  • Stakeholder needs (what decisions will this inform?)

2. Identify Weak Signals

Weak signals are early indicators of emerging trends. Sources:

  • Academic research and conference papers (BlackHat, DEF CON, CCC, academic journals)
  • Underground forum discussions (new tools, techniques being discussed)
  • Patent filings and startup activity (indicators of new capabilities)
  • Geopolitical developments (sanctions, conflicts, elections)
  • Regulatory changes (new compliance requirements creating new attack surfaces)
  • Technology adoption trends (new tech = new attack surface)

3. Categorise Signals

Category Examples
Emerging TTPs New exploitation techniques, novel social engineering methods, AI-augmented attacks
Technology shifts New platforms widely adopted, legacy tech being deprecated, cloud migration patterns
Threat actor evolution New groups emerging, existing groups changing targets, capability development
Geopolitical drivers Conflicts, sanctions, elections, diplomatic shifts
Regulatory/legal New laws, enforcement actions, liability changes
Underground economy New services, market shifts, ecosystem changes

4. Develop Scenarios

For each significant signal, develop three scenarios:

  • Best case: Signal does not materialise or is mitigated
  • Worst case: Signal materialises with maximum impact
  • Most likely: Balanced assessment based on available evidence

5. Assess Impact and Likelihood

For each scenario:

  • Likelihood (using probability yardstick from likelihood-language skill)
  • Impact on organisation (Critical/High/Moderate/Low/Negligible)
  • Time to materialise
  • Confidence in assessment

Read the full file on GitHub · 97 lines

Changes

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.

  1. 12d ago First seen · 97 lines · 44 tokens per session scan A d6d4a938d87d

Subscribe to this mod's changes

horizon-scanning is a skill published in the GitHub repository Liberty91LTD/cti-skills (18 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 823 once invoked, about $0.0002 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-30.