audience

audience is a skill for Claude Code from fiber-ai/fiber-ai-plugin. It costs 44 tokens per session (1,757 once invoked), scanned A, original, MIT.

A Fiber AI audience workflow for building and managing saved lists of companies or contacts for bulk searching, enrichment, and export. An audience is a reusable list that moves through stages such as building, enriching, and exporting.

In plain words
What is it for?
Use it to create prospecting lists, enrich more than five contacts in bulk, and export the resulting company or contact data.
Why use it?
It organizes large prospecting or data-enrichment jobs into a defined process instead of handling each record separately.

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

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.

agentmods
npx agentmods add skills/fiber-ai/fiber-ai-plugin/audience
Any agent
npx skills add fiber-ai/fiber-ai-plugin --skill audience
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 audience

README.md
[![agentmods](https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/audience.svg)](https://agentmods.dev/skills/fiber-ai/fiber-ai-plugin/audience)
Your own site
<a href="https://agentmods.dev/skills/fiber-ai/fiber-ai-plugin/audience"><img src="https://agentmods.dev/badge/skills/fiber-ai/fiber-ai-plugin/audience.svg" alt="Measured on agentmods" 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 1,757 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.01757
Opus 5 $0.00022 $0.00879
Sonnet 5 $0.00009 $0.00351
Haiku 4.5 $0.00004 $0.00176

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

Security

Grade A, and why

audience 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 6d 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/audience/SKILL.md · 148 lines

How it starts

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

Fiber AI Audience Workflow

Audiences are the core workflow for bulk operations in Fiber AI. They allow searching, enriching, and exporting lists at scale.

For the complete, up-to-date workflow guide, read the MCP resource llms://fiber.ai/docs/audience-workflow via the Core MCP.

When to Use

  • User wants to build a prospecting list
  • User wants to bulk enrich contacts (more than 5 people)
  • User wants to export data to CSV or download a list
  • User says "create audience", "build list", "bulk enrich", "export", "prospecting list"

Do Not Use When

  • User wants to search without saving results — use /fiber:search instead
  • User wants to enrich a single contact — use /fiber:enrich instead
  • User wants to write code for audience management — use /fiber:sdk-ts or /fiber:sdk-py instead

The Audience Lifecycle

Each step must be completed in order. Do not skip steps. Build and enrichment are async — you must poll for completion.

Create → Set Search Params → Build → Poll Build Status → Estimate Cost → Enrich → Poll Enrichment Status → Export

How to Execute

All audience operations must go through the Core MCP using call_operation. They are not available as V2 direct tools.

Before calling any operation, use get_endpoint_details_full("operationId") to get the exact parameter schema. Parameters change over time — do not guess field names.

Step 1: Create Audience

  • operationId: createAudience
  • Method: POST /v1/audiences/create
  • apiKey goes in the request body
  • Save the returned audience ID for all subsequent steps
  • Confirm creation with the user

Step 2: Set Search Parameters

  • operationId: updateAudienceSearchParams
  • Method: PATCH /v1/audiences/{audienceId}/search-params
  • apiKey goes in the request body
  • The body contains companySearchParams and/or prospectSearchParams — these are separate filter objects with different schemas
  • Call get_endpoint_details_full("updateAudienceSearchParams") to see available filter fields
  • Show the user what filters were applied and confirm before proceeding
  • Can only be set while audience status is DRAFT

Read the full file on GitHub · 148 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. 6d ago First seen · 148 lines · 44 tokens per session scan A c604e8c89e33

Subscribe to this mod's changes

audience is a skill published in the GitHub repository fiber-ai/fiber-ai-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,757 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-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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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