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 X-School-Academy/skill-pilot --skill background-promptgit clone --depth 1 https://github.com/X-School-Academy/skill-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/x-school-academy/skill-pilot/background-prompt)<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/background-prompt"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/background-prompt/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/x-school-academy/skill-pilot/background-prompt"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/background-prompt.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.00044 | $0.00462 |
| Opus 5.5 | $0.00018 | $0.00185 |
| Sonnet 5.5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
background-prompt 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 16d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Background Prompt
Run a prompt as a background task through the local core/bin/agent-cli tool.
When to Use This Skill
- User wants to execute a prompt in the background
- User wants a prompt executed by the default core engine LLM provider
- The task is suitable for single-prompt inference with plain text output
Your Roles in This Skill
- Backend Developer (Engineer): Execute the tool command and capture output safely
- Technical Writer: Convert tool output into a clear user-facing response
- Security Engineer: Ensure prompt execution follows configured security flags
Role Communication
As an expert in your assigned roles, you must announce your actions before performing them using the following format:
As a {Role, and Role-XYZ if have more roles}, I will {action description}
This communication pattern ensures transparency and allows for human-in-the-loop oversight at key decision points.
Instructions
Follow these steps in order:
Step 1: Confirm intent
Ensure the user wants to run a background prompt. If not explicit, ask for confirmation before invoking.
Step 2: Build the prompt
Compose one concise prompt string from user instructions. Keep task scope explicit and include required output format details.
Step 3: Execute Agent CLI
Run from repository root:
core/bin/agent-cli "<prompt>"
Optional overrides only if user requests:
core/bin/agent-cli --provider <provider-id> --sandbox --auto --network "<prompt>"
Step 4: Return plain text result
Return the command output as plain text to the user. If command fails, include the error text and a concrete retry suggestion.
Expected Output
- A plain text response generated by
core/bin/agent-cli - Any execution error surfaced clearly when failures occur
Key Principles
- Use
core/bin/agent-clias the primary execution path - Keep prompts specific and deterministic
- Respect configured security defaults unless user requests overrides
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.
- 16d ago First seen · 70 lines · 44 tokens per session scan A ff8f060f22e0
background-prompt is a skill published in the GitHub repository X-School-Academy/skill-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 462 once invoked, about $0.0002 per session on Opus 5.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-10-02.
Other skills, from other repositories
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.