PrompterOne: Agent for Claude Code

.codex/skills/dotnet-microsoft-agent-framework/references/official-docs/user-guide/agents/agent-background-responses.md

agent-background-responses is an agent for Claude Code, Codex from managedcode/PrompterOne. It costs 13 tokens per session (2,020 once invoked), scanned A, original, MIT.

A guide to handling responses from software agents when their work takes too long to finish in one request.

In plain words
What is it for?
It explains how to start background processing, receive an immediate result or continuation token, and later poll for or resume the agent's response.
Why use it?
It helps applications avoid timeouts or interruptions during complex, long-running tasks. The application can check back later using a continuation token.

Agent for Claude CodeCodex

Written for Codex and Claude Code: installed under .codex/, but also a Claude Code subagent (agents/*.md).

This is managedcode/PrompterOne's own configuration. It tells Claude Code and Codex how to work on PrompterOne itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PrompterOne configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is [Using MCP Tools](../model-context-protocol/using-mcp-tools.md).

Reuse

Borrowing it

Nothing to install: this file belongs to managedcode/PrompterOne. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/managedcode/PrompterOne/main/.codex/skills/dotnet-microsoft-agent-framework/references/official-docs/user-guide/agents/agent-background-responses.md
Clone the repo
git clone --depth 1 https://github.com/managedcode/PrompterOne

Made for: Claude Code, Codex.

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 agent-background-responses

README.md
[![agentmods](https://agentmods.dev/badge/agents/managedcode/prompterone/agent-background-responses/github.svg)](https://agentmods.dev/agents/managedcode/prompterone/agent-background-responses)
Your own site
<a href="https://agentmods.dev/agents/managedcode/prompterone/agent-background-responses"><img src="https://agentmods.dev/badge/agents/managedcode/prompterone/agent-background-responses/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 agent-background-responses

Your own site · 80×15
<a href="https://agentmods.dev/agents/managedcode/prompterone/agent-background-responses"><img src="https://agentmods.dev/badge/agents/managedcode/prompterone/agent-background-responses.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,020 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.
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.00013 $0.02020
Opus 5.5 $0.00005 $0.00808
Sonnet 5.5 $0.00003 $0.00404
Haiku 4.5 $0.00001 $0.00202

Measured 1mo ago against content hash deec666bc177, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-background-responses 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 1mo 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.

.codex/skills/dotnet-microsoft-agent-framework/references/official-docs/user-guide/agents/agent-background-responses.md · 214 lines

How it starts

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

Agent Background Responses

The Microsoft Agent Framework supports background responses for handling long-running operations that may take time to complete. This feature enables agents to start processing a request and return a continuation token that can be used to poll for results or resume interrupted streams.

[!TIP] For a complete working example, see the Background Responses sample.

When to Use Background Responses

Background responses are particularly useful for:

  • Complex reasoning tasks that require significant processing time
  • Operations that may be interrupted by network issues or client timeouts
  • Scenarios where you want to start a long-running task and check back later for results
  • Long-running tasks that also invoke function tools during background processing

How Background Responses Work

Background responses use a continuation token mechanism to handle long-running operations. When you send a request to an agent with background responses enabled, one of two things happens:

  1. Immediate completion: The agent completes the task quickly and returns the final response without a continuation token
  2. Background processing: The agent starts processing in the background and returns a continuation token instead of the final result

The continuation token contains all necessary information to either poll for completion using the non-streaming agent API or resume an interrupted stream with streaming agent API. When the continuation token is null, the operation is complete - this happens when a background response has completed, failed, or cannot proceed further (for example, when user input is required).

::: zone pivot="programming-language-csharp"

Enabling Background Responses

To enable background responses, set the AllowBackgroundResponses property to true in the AgentRunOptions:

AgentRunOptions options = new()
{
    AllowBackgroundResponses = true
};

Read the full file on GitHub · 214 lines

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. 1mo ago First seen · 214 lines · 13 tokens per session scan A deec666bc177

Subscribe to this mod's changes

agent-background-responses is an agent published in the GitHub repository managedcode/PrompterOne (45 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 2,020 once invoked, about $0.0001 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-08-30.