feedback-loops

feedback-loops is a skill for Claude Code from Liberty91LTD/cti-skills. It costs 24 tokens per session (713 once invoked), scanned A, original, MIT.

A process guide for improving cyber-threat intelligence through repeated feedback. Cyber-threat intelligence is information about digital threats, attackers, and risks used to support decisions.

In plain words
What is it for?
Collecting stakeholder feedback, running retrospective reviews, assessing source quality, and adjusting intelligence collection and reporting.
Why use it?
It helps teams learn whether their intelligence was useful, timely, and appropriately formatted, while tracking which information sources remain reliable.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Collecting stakeholder feedback, running retrospective reviews, assessing source quality, and adjusting intelligence collection and reporting.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/liberty91ltd/cti-skills/feedback-loops
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 feedback-loops
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 feedback-loops

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/feedback-loops"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/feedback-loops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 713 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.00024 $0.00713
Opus 5 $0.00012 $0.00357
Sonnet 5 $0.00005 $0.00143
Haiku 4.5 $0.00002 $0.00071

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

Security

Grade A, and why

feedback-loops 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 11d 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/feedback-loops/SKILL.md · 99 lines

How it starts

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

Feedback Loops

Feedback is Phase 6 of the CTI Hyperloop. Without it, the cycle is open-ended and quality degrades over time.

Types of Feedback

1. Consumer Feedback

Intelligence consumers (stakeholders) assess the value of products they receive.

Collection points:

  • After every significant product delivery
  • During quarterly PIR reviews
  • During stakeholder briefings

Questions:

Question Response Options
Was this intelligence useful for your decision-making? Very useful / Somewhat useful / Not useful
Was it delivered in time to act on? Yes / Partially / No
Was the format appropriate for your needs? Yes / Too technical / Too high-level / Wrong format
Was the confidence assessment helpful? Yes / Unclear / Not included
What should we prioritise next? Free text

Actions:

  • Useful + timely → Continue current approach, reinforce collection sources
  • Useful + late → Improve detection/triage speed, adjust collection frequency
  • Not useful → Review PIR alignment, stakeholder needs, product format
  • Format wrong → Adjust per stakeholder-management skill

2. Source Quality Tracking

Track the reliability of intelligence sources over time.

For each source used in products:

  • Was the information confirmed, partly confirmed, or disproven?
  • Did the source's Admiralty rating need adjustment?
  • Were there timeliness issues?

Actions:

  • Consistently confirmed → Upgrade reliability rating (e.g., C → B)
  • Inconsistent → Maintain or downgrade rating
  • Repeatedly disproven → Downgrade to D or E
  • Feed updates into source-assessment guidance

3. Analyst Retrospectives

After significant investigations or assessments:

Questions:

  • What analytical techniques were applied? Were they effective?
  • Were key assumptions validated or invalidated?
  • Were there intelligence gaps that could have been filled?
  • Were alternative hypotheses adequately considered?
  • What would you do differently?

Read the full file on GitHub · 99 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. 11d ago First seen · 99 lines · 24 tokens per session scan A 16ba39ddcff6

Subscribe to this mod's changes

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