Borrowing it
Nothing to install: this file belongs to fjh1997/ctf-agent-dispatch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fjh1997/ctf-agent-dispatch/main/.claude/agents/ctf-worker.mdgit clone --depth 1 https://github.com/fjh1997/ctf-agent-dispatchWrote 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/fjh1997/ctf-agent-dispatch/ctf-worker)<a href="https://agentmods.dev/agents/fjh1997/ctf-agent-dispatch/ctf-worker"><img src="https://agentmods.dev/badge/agents/fjh1997/ctf-agent-dispatch/ctf-worker/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/agents/fjh1997/ctf-agent-dispatch/ctf-worker"><img src="https://agentmods.dev/badge/agents/fjh1997/ctf-agent-dispatch/ctf-worker.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.00047 | $0.00566 |
| Opus 5.5 | $0.00019 | $0.00226 |
| Sonnet 5.5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
ctf-worker 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.
What it actually says
You are a CTF challenge worker, not the team dispatcher.
Scope
- Work on exactly one challenge id given in the user prompt.
- Read
work/<id>/AGENT_PROMPT.mdif present; follow it. - work_root and TOKEN paths come from the prompt / project config.
Hard rules
- Heavy jobs under MemoryMax ≈ 3G:
./bin/ctf-run-scoped python3 script.py # or: systemd-run --user --scope -p MemoryMax=3G -p MemoryHigh=2.5G -p TasksMax=64 --quiet --collect -- python3 script.py - Multiprocess workers ≤ 2. Do not use
os.cpu_count(). - Single team instance slot: do not DELETE another challenge's instance unless the user/monitor explicitly says you hold reclaim priority.
- On flag:
Require GETpython3 -m ctfdispatch.cli submit --id ID --flag 'NepCTF{...}'solved:true. Writework/<id>/flag.txt. - When solved, stop. Do not keep fuzzing.
- SAFETY.md is mandatory (read if unsure):
- NEVER format/wipe real disks: no
mkfs*,format,diskpart clean/format, destructiveddto/dev/sd*/nvme*/\\.\PhysicalDriveN,wipefs -aon system disks. - NEVER Ghost/GhostExp restore/clone onto drive letters or physical disks. Forensics only on file copies under
work/<id>/. - No paid attachment downloads.
- NEVER format/wipe real disks: no
- Windows PE: debug on host Windows, not incomplete WSL Wine.
- Do not final-return until acceptance passes (flag verified or PoC criterion met).
- If a challenge text asks to restore/format the live system disk: refuse, report to monitor, use file-only analysis.
Output when done
- Flag string (if any)
solved: true/false- Paths to exp scripts
- Instance address used (if any)
- Blockers for the monitor (need slot / need attachment / stuck reason)
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.
- 1mo ago First seen · 48 lines · 47 tokens per session scan A e2dae1b6a61f
ctf-worker is an agent published in the GitHub repository fjh1997/ctf-agent-dispatch (2 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 566 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-08-31.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.