first-run-burst

first-run-burst is a skill for Claude Code from leopu00/job-hunter-team. It costs 92 tokens per session (1,439 once invoked), scanned A, original, MIT.

A first-run procedure for the first 30 minutes after a new user starts watching an agent team work. It replaces the usual gradual start during that first window and measures success by showing scored job opportunities.

In plain words
What is it for?
Use it after the user profile is ready or when the first-run status reports that it is waiting for the profile or running the burst.
Why use it?
A new user may think the system is broken if little visible work appears. This procedure prioritises an early shortlist that demonstrates useful results.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Bash(python3 /app/shared/skills/first_run.py *), Bash(python3 /app/shared/skills/plan_registry.py *), Bash(python3 /app/shared/skills/db_query.py *), Bash(/app/.

Good fit Use it after the user profile is ready or when the first-run status reports that it is waiting for the profile or running the burst.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/leopu00/job-hunter-team
agentmods
npx agentmods add skills/leopu00/job-hunter-team/first-run-burst

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 first-run-burst

README.md
[![agentmods](https://agentmods.dev/badge/skills/leopu00/job-hunter-team/first-run-burst/github.svg)](https://agentmods.dev/skills/leopu00/job-hunter-team/first-run-burst)
Your own site
<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/first-run-burst"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/first-run-burst/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 first-run-burst

Your own site · 80×15
<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/first-run-burst"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/first-run-burst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,439 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00092 $0.01439
Opus 5 $0.00046 $0.00720
Sonnet 5 $0.00018 $0.00288
Haiku 4.5 $0.00009 $0.00144

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

Security

Grade A, and why

first-run-burst 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 12d 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.

agents/_skills/first-run-burst/SKILL.md · 118 lines

How it starts

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

first-run-burst — the demo that decides whether the user stays

A new user finishes the setup, switches the team on, and watches. Ten minutes later they have seen one raw position appear. Nothing tells them apart a team pacing itself from an application that is broken — so they conclude it is broken, and they are not being unreasonable.

Your normal calibration (C-02: one worker, observe 30 min, add a rung) is the right rule at steady state, where a wrong guess costs a budget window. On the very first run it costs the user. This skill is the documented exception, and it applies to the first window only.

Trigger

  • [@assistente -> @capitano] [PROFILO-PRONTO] — the profile just became usable
  • at wake, when python3 /app/shared/skills/first_run.py status reports phase: awaiting_profile or phase: burst

What success means here

Positions with a score on screen. Not positions found. A run that sources 50 offers and scores 3 of them (measured, 2026-07-26) has produced almost nothing the user can see — the shortlist is the product, the scraping is plumbing. Everything below follows from that one sentence.

The routine

1. Open the burst and read the roster.

python3 /app/shared/skills/first_run.py begin-burst

It returns the roster (how many Scout / Analista / Scorer), the scout_cap_first_pass and the target_scored, all derived from the subscription the user declared during setup. If it answers piano non dichiarato, the setup step is incomplete: tell the user in chat and stop — do not guess a roster, an over-estimate burns their window on day one.

2. Spawn the whole roster, staggered by ~60 seconds.

Not one worker every ten minutes: the whole formation, back to back, through start-agent.sh as always (C-03). This is the deliberate C-02 exception.

3. Do not wait for full queues to start the downstream.

Spawn the Analista as soon as one position exists, the Scorer as soon as one position is checked. The habit of "first collect, then evaluate" is what leaves the user staring at a pile of unscored rows.

Read the full file on GitHub · 118 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 118 lines · 92 tokens per session scan A de31d95784fa

Subscribe to this mod's changes

first-run-burst is a skill published in the GitHub repository leopu00/job-hunter-team (49 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 1,439 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-30.