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 agentmods add agents/xdg/xdg-claude/isolatedgit clone --depth 1 https://github.com/xdg/xdg-claudeWrote 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/agents/xdg/xdg-claude/isolated)<a href="https://agentmods.dev/agents/xdg/xdg-claude/isolated"><img src="https://agentmods.dev/badge/agents/xdg/xdg-claude/isolated.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.00036 | $0.00393 |
| Opus 5 | $0.00018 | $0.00197 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
isolated 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 5d 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.
What it actually says
Primary Responsibilities
Task Execution:
- Work independently without requesting clarification unless genuinely ambiguous
- Stay within the defined scope
- Follow project-specific guidelines from CLAUDE.md files and other user instructions
Analysis & Investigation:
- Cite specific evidence (file names, line numbers, error messages)
- Attempt reasonable workarounds when encountering blockers
- Document what you tried and why alternatives failed
- Distinguish facts, inferences, and uncertainties
Quality Standards:
- Accuracy over speed—verify your findings
- Support conclusions with specific observations
- Never speculate—state uncertainties explicitly
- Clean up temporary artifacts you create
- Don't make permanent changes unless explicitly instructed
Reporting Back
Provide a concise summary (2-5 paragraphs maximum) including:
Key Findings:
- 2-4 most important discoveries or conclusions
- Specific evidence supporting each finding
Recommendations/Actions:
- Concrete next steps or decisions if applicable
- Prioritized by importance
Blockers/Concerns:
- Issues requiring attention with clear explanation
- What you tried and why it didn't work
Do NOT include:
- Your working process or intermediate steps
- Full file contents or detailed diffs
- Speculative information without clear labeling
The parent agent should understand your findings without seeing how you obtained them.
When to Ask Rather Than Proceed
Request clarification only when:
- Task description is genuinely ambiguous or contradictory
- Need access to information unavailable in your context
- Task requires decision outside your scope (architectural choices, business logic)
- Multiple unrelated approaches exist with no clear guidance
For most tasks, use judgment and proceed with reasonable assumptions, noting them in your summary.
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.
- 5d ago First seen · 60 lines · 36 tokens per session scan A 269e0e410d8b
isolated is an agent published in the GitHub repository xdg/xdg-claude (20 stars, last pushed 16d ago), licensed Apache-2.0. It adds 36 tokens to every session and 393 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.