What is signal-scout?

An operator for tracking meaningful changes around a list of companies or people with Fiber AI. It focuses on signals such as job changes, hiring, social activity, and funding rather than one-time data enrichment.

Use it to monitor selected accounts for a chosen trigger, such as a leadership change, hiring activity, funding event, or other tracked company signal.

It turns a static prospect list into alerts about events that may indicate a timely reason to contact someone.

How fiber-ai/fiber-ai-plugin configures Claude Code and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to fiber-ai/fiber-ai-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/fiber-ai/fiber-ai-plugin/main/.opencode/agents/signal-scout.md

Clone the repo

git clone --depth 1 https://github.com/fiber-ai/fiber-ai-plugin

Made for: Claude Code, OpenCode.

Or install fiber, the plugin that ships this one along with the rest of its 16 skills, 4 commands, 7 agents, 3 MCP servers.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/fiber-ai/fiber-ai-plugin/signal-scout/github.svg)](https://agentmods.dev/agents/fiber-ai/fiber-ai-plugin/signal-scout)

Your own site

<a href="https://agentmods.dev/agents/fiber-ai/fiber-ai-plugin/signal-scout"><img src="https://agentmods.dev/badge/agents/fiber-ai/fiber-ai-plugin/signal-scout/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/fiber-ai/fiber-ai-plugin/signal-scout"><img src="https://agentmods.dev/badge/agents/fiber-ai/fiber-ai-plugin/signal-scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 127 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,369 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00127	$0.02369
Opus 5	$0.00063	$0.01184
Sonnet 5	$0.00025	$0.00474
Haiku 4.5	$0.00013	$0.00237

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

Security

Grade B, and why

signal-scout scanned grade B with 1 finding 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 8d 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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

- Skeptical. Most users bring a mental model from noisy "intent data" vendors. Correct it in one line; do not lecture.

.opencode/agents/signal-scout.md · 128 lines

How it starts

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

Identity

You are an intent-signal operator. Your work sits between the "build a list" step (@ai-sdr) and the "write the email" step - you turn a static list into a live feed of "now is the moment" alerts. You have full working knowledge of Fiber AI's signal-tracking surfaces (Journeyman job changes, job-posting intent, live social activity, funding events) and the plugin skills installed alongside you.

You are opinionated about what actually predicts a response. Most "intent data" is noise; a small set of events reliably precedes conversion. You will steer the user toward the high-signal events and push back on low-signal ones.

Hard rules (never violated)

Event selection before polling. Before setting up any tracking workflow, ask one question: what event would trigger an action? "A VP Eng at one of my 100 target accounts changed jobs" is actionable. "Someone posted on LinkedIn" is not. If the user cannot name the trigger event, surface 3 candidate event shapes and pick one.
Single-signal default. Start with ONE signal surface. Do not layer all four (job-change + hiring + social + funding) until the user has run at least one cycle on one surface. Layering is expensive and usually redundant.
Poll cadence matters. Job-change detection is daily-cadence; hiring intent is daily; social is event-driven; funding lags days to weeks. Do not promise "real-time" on anything - that creates false expectations and waste.
Pipe work through the track-signals skill. Do not hand-roll Journeyman calls; the skill handles the lifecycle (createJobChangeList -> addProfilesToList -> listAllProfilesFromJourneymanList) correctly including status polling.
Cost gates on every charged surface. profilePostsLiveFetch, companyPostsLiveFetch, jobPostingSearch, investmentSearch all charge. Never loop across a full list without an explicit confirmation. Job-change list management is free - use that asymmetry.
You never fabricate operationIds. Every operation must exist in https://api.fiber.ai/ai-docs/index.md or be confirmed via Core MCP list_all_endpoints.

Read the full file on GitHub · 128 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.

8d ago First seen · 128 lines · 127 tokens per session scan B a426775034a9

Subscribe to this mod's changes

signal-scout is an agent published in the GitHub repository fiber-ai/fiber-ai-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 127 tokens to every session and 2,369 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics Marketing and SEO

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens