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 patleeman/neon-pilot --skill runsgit clone --depth 1 https://github.com/patleeman/neon-pilotWrote 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/patleeman/neon-pilot/runs)<a href="https://agentmods.dev/skills/patleeman/neon-pilot/runs"><img src="https://agentmods.dev/badge/skills/patleeman/neon-pilot/runs/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.
<a href="https://agentmods.dev/skills/patleeman/neon-pilot/runs"><img src="https://agentmods.dev/badge/skills/patleeman/neon-pilot/runs.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00610 |
| Opus 5 | $0.00012 | $0.00305 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
background-work 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Background Work
Use intent-shaped tools. For waiting/resuming this conversation later, use the unified conversation deferred-resume admin command; do not run sleep in bash.
Choose the tool
| Tool | Use case |
|---|---|
bash |
Shell commands; set background: true for durable background commands. |
background_bash |
Lifecycle tool for background command records. |
subagent |
A delegated agent task that should run durably outside the current turn. |
scheduled_task |
A persistent automation with a cron/time trigger and delivery policy. |
| the unified conversation deferred-resume admin command | Continue this same conversation later. |
Background commands
Completion delivery is the normal “wake me when this finishes” path. If a background command/subagent uses deliverResultToConversation: true, do not also schedule a the unified conversation deferred-resume admin command merely to check whether it finished. Only schedule a separate wakeup for a distinct time-based action that should happen regardless of completion timing, and include a clear reason.
For Neon Pilot administration from shell, prefer the CLI equivalents:
neon-pilot background-commands list --json
neon-pilot background-commands start --command "pnpm test" --cwd /repo --json
neon-pilot background-commands logs <run-id> --tail 200 --json
neon-pilot background-commands cancel <run-id> --json
Start a detached command with bash:
{
"command": "npm test",
"background": true,
"taskSlug": "tests",
"cwd": "/path/to/repo"
}
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.
- 9d ago First seen · 72 lines · 24 tokens per session scan A 9dfdec14f7ff
background-work is a skill published in the GitHub repository patleeman/neon-pilot (23 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 610 once invoked, about $0.0001 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.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.