track-signals

track-signals is a skill for Claude Code from fiber-ai/fiber-ai-plugin. It costs 125 tokens per session (2,450 once invoked), scanned A, original, MIT.

A Fiber AI monitoring skill that watches known people or companies for job changes, job postings, LinkedIn activity, and funding rounds.

In plain words
What is it for?
It is for tracking hiring intent, funding, job changes, and social activity over time.
Why use it?
It turns a fixed list of accounts into an ongoing feed of changes that may show hiring or buying interest.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the fiber plugin — 16 skills, 4 commands, 7 agents, 3 MCP servers shipped together

Good fit It is for tracking hiring intent, funding, job changes, and social activity over time.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fiber-ai/fiber-ai-plugin/track-signals
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 fiber-ai/fiber-ai-plugin --skill track-signals
Clone the repo
git clone --depth 1 https://github.com/fiber-ai/fiber-ai-plugin

Made for: Claude Code.

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.

agentmods badge for track-signals

README.md
[![agentmods](https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/track-signals/github.svg)](https://agentmods.dev/skills/fiber-ai/fiber-ai-plugin/track-signals)
Your own site
<a href="https://agentmods.dev/skills/fiber-ai/fiber-ai-plugin/track-signals"><img src="https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/track-signals/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 track-signals

Your own site · 80×15
<a href="https://agentmods.dev/skills/fiber-ai/fiber-ai-plugin/track-signals"><img src="https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/track-signals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,450 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.00125 $0.02450
Opus 5 $0.00063 $0.01225
Sonnet 5 $0.00025 $0.00490
Haiku 4.5 $0.00013 $0.00245

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

Security

Grade A, and why

track-signals 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 9d 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/track-signals/SKILL.md · 127 lines

How it starts

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

Fiber AI: Track Signals

Turn a static list of people or companies into a live intent feed. Fiber exposes four orthogonal signal surfaces; this skill composes them based on what the user is trying to trigger on.

When to use

  • User has a seed list of people or companies and wants ongoing alerts, not a one-shot enrichment
  • User asks to "track job changes", "monitor these accounts", "set up hiring alerts", "watch for funding rounds", "alert me when X happens at these companies"
  • User wants to build a signal-driven outbound cadence ("reach out whenever someone changes jobs")
  • User wants a recruiting pipeline driven by "open to work" / recent-title-change signals

Do not use when

  • User wants a one-shot contact reveal - use /fiber:enrich or /fiber:enrich-linkedin-csv
  • User wants to discover new accounts, not monitor known ones - use /fiber:find-similar-companies or /fiber:search
  • User needs a persistent exportable audience of 100+ prospects - use /fiber:audience or /fiber:build-recruiting-audience (those are build-then-export flows, not monitor-over-time)

Happy path

Pick the signal type based on what the user is trying to trigger on. Do not bundle all four by default - each carries its own cost and cadence.

A. Job-change signals (native, recommended default)

Fiber exposes a first-class Journeyman / job-change list. Run it once, poll forever.

  1. Create a list with createJobChangeList. Free.
  2. Add profiles in one pass with addProfilesToList. The list transitions to BUILDING, then NORMAL.
  3. Poll getJourneymanList until status === "NORMAL". For large lists wait, don't busy-loop.
  4. Read current state with listAllProfilesFromJourneymanList. Each row carries the last observed company / title plus any change detected since the last poll.
  5. On an ongoing basis, the user re-polls (step 4) on whatever cadence they want. Flag each row where company or title changed since last known state.

Read the full file on GitHub · 127 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. 9d ago First seen · 127 lines · 125 tokens per session scan A c84ce57448ea

Subscribe to this mod's changes

track-signals is a skill published in the GitHub repository fiber-ai/fiber-ai-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 125 tokens to every session and 2,450 once invoked, about $0.0006 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens