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.
npx agentmods add skills/fiber-ai/fiber-ai-plugin/quickstartnpx skills add fiber-ai/fiber-ai-plugin --skill quickstartgit clone --depth 1 https://github.com/fiber-ai/fiber-ai-pluginWhat 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 | $0.00094 | $0.01443 |
| Opus 5 | $0.00047 | $0.00722 |
| Sonnet 5 | $0.00019 | $0.00289 |
| Haiku 4.5 | $0.00009 | $0.00144 |
Grade A, and why
quickstart 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fiber AI: Quickstart
Prove Fiber's value in under 60 seconds. This skill chains three operations into a single guided flow: verify credentials, search for relevant companies, and reveal one real contact with verified email. Designed for the moment right after installation when the user is deciding whether to keep using Fiber.
When to use
- User just installed the Fiber plugin and wants to see it work
- User says "quickstart", "get started", "demo", "try Fiber", "show me what Fiber can do"
- User seems uncertain about what Fiber does or how to use it
- User has not yet run any Fiber operation in this session
Do not use when
- User already knows what they want (a specific search, enrichment, or audience) - route to the relevant skill directly
- User wants to set up API key only without running anything - use
/fiber:setup - User wants a full benchmark or data-quality test - use
/fiber:benchmark-vs-competitor
Happy path
Step 1: verify credentials (5 seconds)
- Check if
FIBER_API_KEYis set in the environment. - If not set, tell the user: "Set your API key first:
export FIBER_API_KEY=sk_live_...(get one free at https://fiber.ai/app/api)." Stop here until the key is set. - Call
getOrgCreditsto verify the key works. Show: "Connected. You have N credits available."
Step 2: find relevant companies (15 seconds)
- Ask ONE question: "What industry or type of company are you interested in?" If the user provided an argument (e.g.
/fiber:quickstart fintech), skip the question and use that. - Call
companySearchwith a tight filter based on the user's answer. SetpageSize: 5. - Display the 5 results as a compact table: company name, domain, industry, headcount, location. Example:
Found 5 companies matching "fintech, Series B+":
| Company | Domain | Industry | Headcount | Location |
| ------------- | --------------- | --------- | --------- | ----------- |
| Acme Pay | acmepay.com | Fintech | 200 | San Francisco |
| ... | ... | ... | ... | ... |
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.
- 2d ago First seen · 102 lines · 94 tokens per session scan A 9764cc219fc0
quickstart is a skill published in the GitHub repository fiber-ai/fiber-ai-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 94 tokens to every session and 1,443 once invoked, about $0.0005 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…