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 skills add wrg32786/aigent-os --skill first-wingit clone --depth 1 https://github.com/wrg32786/aigent-osWrote 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.
[](https://agentmods.dev/skills/wrg32786/aigent-os/first-win)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/first-win"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/first-win.svg" alt="Measured on agentmods" height="20"></a>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.00061 | $0.00602 |
| Opus 5 | $0.00030 | $0.00301 |
| Sonnet 5 | $0.00012 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
first-win 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/first-win: ship something real, today
The operator has just met you (via /operator-setup). Now give them proof of work: a real
artifact they can use today. This is what satisfies the "ship something real, fast" promise
on day one, instead of making them wait for a longer pipeline.
The menu
Offer these three. Lead with the two zero-dependency tasks so the win never stalls waiting on an inbox connection or any login beyond their Claude account:
-
Turn your last post into a week of social posts. (zero-dependency, default) Ask them to paste their most recent newsletter, blog post, or even a few sentences about what they do. Produce five to seven platform-ready posts in their voice, each with a clear hook. If they have nothing to paste, use the known-good example below so they still get a result.
-
Turn a rough idea into a structured plan. (zero-dependency, default) Ask for the idea in a sentence. Produce a structured plan: the outcome, the steps in order, the first action they can take today, and what "done" looks like. Concrete, not generic.
-
Today's three priorities from your inbox. (only if connected) If an inbox connector is set up, summarize their inbox into three priorities for today. If not, they paste a handful of emails or notes and you do the same thing. Never block on OAuth or a connector. This task always has the paste-in fallback.
Delivery
- Produce the artifact directly in the session, formatted cleanly, ready to use or copy.
- Then ask: "Want to tweak it, or save it and move on?" Keep it conversational.
Known-good example inputs (so a blank-page operator always gets a result)
- For task 1: a short sample post about a local trades bookkeeping practice, which you turn into a week of social posts as a demonstration, then offer to redo it with their real content.
- For task 2: "I want to start a weekly email for my customers" as the rough idea, which you turn into a structured plan.
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.
- 6d ago First seen · 51 lines · 61 tokens per session scan A 2e115b2bcccc
first-win is a skill published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 602 once invoked, about $0.0003 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-09-01.
Other skills, from other repositories
send-email
Compose and send a one-off email to a named recipient via Resend - written in the operator's voice, then sent in-run through the shared send caps with an operator audit copy.
RemoteTeamCommander
Complete operating system for remote and distributed teams — async communication, time zone equity, virtual culture, performance management at a distance, and preventing remote-class citizens.
chief-of-staff
Act as the user's chief of staff, not a task-taker. Use for planning a day or week, triaging priorities, prepping for meetings or calls, drafting messages on the user's behalf, tracking commitments and follow-ups, reviewing what's in-flight, or any moment the user wants a trusted operator who knows their context.…
meeting-analyzer
Activates MeetingAnalyzer for extracting intelligence from meeting transcripts, notes, and recordings. Use when you need to extract action items with owners and due dates, identify decisions made, summarize key discussion points, detect unresolved conflicts or blockers, or generate a structured meeting follow-up email.
Loop
Run the same task on a recurring cron schedule. Parses interval syntax (5m, 2h, 1d, "/15 "), records the schedule, and acknowledges back to the user.
Batch Run
Apply the same prompt or operation to a list of items in turn, collecting results. Useful for "do X to each of these files / PRs / records" tasks.