Background logo

Background

CommunityPopular
jeremylongshore
background

Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage `.hyperflow/background/registry.json` and the per-agent output buffers at `.hyperflow/background/<id>.md`. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents", "what's running in background", "cancel background agent", "show background result".

Overview

Publisherjeremylongshore
Repositorytons-of-skills-marketplace
Skill namebackground
Stars
2.8K
Forks
402
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by jeremylongshore on GitHub. Read the source before you install it.

Installation

Install the Background AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git /tmp/tons-of-skills-marketplace
mkdir -p .claude/skills
cp -r /tmp/tons-of-skills-marketplace/plugins/ai-agency/hyperflow/skills/background .claude/skills/background
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Background in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Background on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Background is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Background

Read-only-by-default management interface for background agents fired by other hyperflow skills (dispatch quality gates, deploy CI watcher, scaffold analysis refresh, cache compact, scope speculative prefetch). Reads from .hyperflow/background/registry.json + per-agent output buffers.

Full doctrine: background-agents.md.

Subcommands

SubcommandDescription
listPrint the registry: in-flight · completed-uncollected · stalled · errored
show <id>Print one agent's output buffer (.hyperflow/background/<id>.md)
cancel <id>Cancel one specific in-flight agent
cancel --allCancel every in-flight agent (use before closing a session)
pruneDelete completed .hyperflow/background/<id>.md files older than 7 days

Default subcommand when none provided: list.

Subcommand Details

list

Read .hyperflow/background/registry.json. Group entries by status and print a compact table:

markdown
## In flight (N)

| ID                                | Purpose                              | Fired      | Timeout | Blocks  |
|-----------------------------------|--------------------------------------|------------|---------|---------|
| `bg-1718049600-quality-gates-b2`  | Layer 5 gates Batch 2                | 17:30      | 18:00   | step3   |
| `bg-1718049820-ci-watcher`        | GitHub Actions watch for v4.7.0      | 17:33      | 18:33   ||

## Completed (uncollected, N)

| ID                                | Purpose                              | Completed  | Duration | Output |
|-----------------------------------|--------------------------------------|------------|----------|--------|
| `bg-1718045400-scaffold-refresh`  | Refresh .hyperflow/architecture.md   | 16:42      | 2m 18s   | 1.4kb  |

## Stalled / Errored (N)

| ID                                | Purpose                              | Status            | Reason            |
|-----------------------------------|--------------------------------------|-------------------|-------------------|
| `bg-1717980000-cache-compact`     | Compact learnings.md                 | STALLED           | timeout (30m)     |

Print one trailing line: <count> in flight · <count> uncollected · <count> needs attention. If registry is empty, print No background agents. and stop.

show <id>

Read .hyperflow/background/<id>.md and print it verbatim. If the agent is still running, print the registry entry first then Output buffer not yet written. and stop.

cancel <id>

  1. Read registry, find the entry.
  2. If status: running, signal cancellation per the provider's mechanism (Claude Code: use the runtime's cancellation API for that subagent ID; if unavailable, mark the entry status: cancelled and leave the agent to time out on its own — the foreground orchestrator will drop the result on collection).
  3. Update registry entry: status: cancelled, cancelled_at: <now>.
  4. Print Cancelled <id> — <purpose>.

If the agent already completed, print Agent <id> already <status> — nothing to cancel.

cancel --all

For every entry with status: running, run the cancel flow. Print summary: Cancelled N agents.

prune

find .hyperflow/background/ -name "bg-*.md" -mtime +7 -delete plus remove their entries from registry.json (only entries with status: complete | error | stalled | cancelled older than 7 days are pruned). Print: Pruned N output buffers · N registry entries.

Flow

  1. Parse subcommand from invocation (default: list).
  2. Read .hyperflow/background/registry.json (if absent, treat as empty).
  3. Execute subcommand.
  4. Print result.

Overview

/hyperflow:background is the user-facing read/manage interface for background agents. The orchestrator itself maintains the registry as a side-effect of run_in_background: true Agent dispatches in other skills — this skill never fires a background agent, it only reads/manages the registry.

Prerequisites

  • .hyperflow/background/registry.json exists (created on first background dispatch by any other skill — if absent, all subcommands degrade gracefully).
  • .hyperflow/ initialized (run /hyperflow:scaffold if missing — though this skill works even without scaffold, since the registry is created on demand).

Instructions

See Subcommands and Subcommand Details. Summary:

  1. Parse the subcommand (default list when none given).
  2. Read the registry from .hyperflow/background/registry.json.
  3. Execute the subcommand against the registry + per-agent output buffers.
  4. Print compact result; do not modify any source code.

Output

  • list — table of in-flight / completed-uncollected / stalled+errored, with one trailing summary line.
  • show <id> — file contents of .hyperflow/background/<id>.md.
  • cancel <id> / cancel --all — one-line confirmation per cancelled agent + total.
  • prune — count of pruned buffers + registry entries.

Error Handling

FailureBehavior
Registry file missingTreat as empty — list prints No background agents.; other subcommands print No registry — fire a background agent first. and stop.
Registry JSON malformedPrint Registry malformed — back up to .hyperflow/background/registry.json.bak and re-create empty. Move file, write empty registry, continue.
show <id> for unknown idList 3 closest IDs by Levenshtein distance.
cancel <id> for already-completed agentPrint Agent <id> already <status> — nothing to cancel.
Provider cancellation API unavailableMark entry status: cancelled in registry; the foreground orchestrator drops the result on collection. Print Marked <id> as cancelled (provider has no live cancellation API — agent will run to completion or timeout, but result will be discarded).
Prune called with no eligible entriesPrint Nothing to prune — no completed buffers older than 7 days.

Examples

List in-flight + completed background agents

/hyperflow:background list

## In flight (1)
| ID                                | Purpose                              | Fired | Timeout | Blocks |
|-----------------------------------|--------------------------------------|-------|---------|--------|
| `bg-1718049600-quality-gates-b2`  | Layer 5 gates Batch 2                | 17:30 | 18:00   | step3  |

## Completed (uncollected, 1)
| ID                                | Purpose                              | Completed | Duration | Output |
|-----------------------------------|--------------------------------------|-----------|----------|--------|
| `bg-1718045400-scaffold-refresh`  | Refresh .hyperflow/architecture.md   | 16:42     | 2m 18s   | 1.4kb  |

1 in flight · 1 uncollected · 0 needs attention

Show a completed agent's output

/hyperflow:background show bg-1718045400-scaffold-refresh

# Background Result — Refresh .hyperflow/architecture.md

| Field      | Value                                |
|------------|--------------------------------------|
| Agent ID   | `bg-1718045400-scaffold-refresh`     |
| Fired at   | 2026-05-16T16:40:00Z                 |
| Completed  | 2026-05-16T16:42:18Z (2m 18s)        |
| Status     | complete                             |
| Tokens     | worker 4.2k                          |

## Output
<refreshed architecture.md content fragments + diff summary>

Cancel everything before closing the session

/hyperflow:background cancel --all

Cancelled bg-1718049600-quality-gates-b2 — Layer 5 gates Batch 2
Cancelled bg-1718049820-ci-watcher — GitHub Actions watch for v4.7.0
Cancelled 2 agents.

Resources

  • background-agents.md — full doctrine: when to use, hard rules, registry shape, failure modes, anti-patterns.
  • DOCTRINE.md — rule 8 (background extensions), rule 9 (no AI-attributed background commits).
  • output-style.md — table conventions for list output.

Frequently asked questions

What does the Background AI skill do?

Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage `.hyperflow/background/registry.json` and the per-agent output buffers at `.hyperflow/background/<id>.md`. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents", "what's running in background", "cancel background agent", "show background result".

Why use Background on TypingMind?

Because you install it once and use it with any model. Background is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Background in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/hyperflow/skills/background. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Background?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Background?

As many as you like. As long as a model supports skills, you can use Background with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Background AI skill free?

Yes. It is published on GitHub by jeremylongshore under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇