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 instructions/alamops/agetor/claude-mdgit clone --depth 1 https://github.com/alamops/agetorWrote 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/instructions/alamops/agetor/claude-md)<a href="https://agentmods.dev/instructions/alamops/agetor/claude-md"><img src="https://agentmods.dev/badge/instructions/alamops/agetor/claude-md.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 | $0.26189 | $0.26189 |
| Opus 5 | $0.13095 | $0.13095 |
| Sonnet 5 | $0.05238 | $0.05238 |
| Haiku 4.5 | $0.02619 | $0.02619 |
Grade F, and why
agetor CLAUDE.md scanned grade F with 5 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 today.
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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
- **`fx`** → driven through `src/bun/fx-acp.ts` — the only driver with **no tmux involved at all**. Vercel Labs' `fx` speaks the Agent Client Protocol (ACP): each turn spawns `fx acp --model <gateway-id> --log-file <data Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- **`fx`** → driven through `src/bun/fx-acp.ts` — the only driver with **no tmux involved at all**. Vercel Labs' `fx` speaks the Agent Client Protocol (ACP): each turn spawns `fx acp --model <gateway-id> --log-file <data Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- **`fx`** → driven through `src/bun/fx-acp.ts` — the only driver with **no tmux involved at all**. Vercel Labs' `fx` speaks the Agent Client Protocol (ACP): each turn spawns `fx acp --model <gateway-id> --log-file <data Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
4. `DELETE /tasks/:id` → `orchestrator.deleteTask` kills any active run, then `removeWorktree` best-effort tears down `git worktree remove --force` + `git branch -D`. If the worktree path still exists afterwards and live Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **`fx`** → driven through `src/bun/fx-acp.ts` — the only driver with **no tmux involved at all**. Vercel Labs' `fx` speaks the Agent Client Protocol (ACP): each turn spawns `fx acp --model <gateway-id> --log-file <data How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
Agetor is a local desktop app that orchestrates CLI coding agents (Claude Code, OpenAI Codex, others) from a kanban board. Each task is a prompt + working directory + agent choice; running it spawns the agent as a child process, streams its stdout/stderr to the UI, and moves the card through columns based on exit status.
It is Electrobun (not Electron) — native webviews driven by a Bun main process. Do not reach for Electron APIs, IPC patterns, or Node-only modules.
Stack and architecture
Two processes share this repo and a small shared types directory:
- Bun main process (
src/bun/) owns the ElectrobunBrowserWindow, a SQLite store, and an HTTP API the webview talks to. The webview is loaded either from the Vite dev server (http://localhost:5173when present) or from the bundledviews://mainview/index.html. - React webview (
src/mainview/) renders the kanban board with dnd-kit, talks to the Bun side overfetch+ SSE, and uses hand-rolled shadcn/ui primitives styled with Tailwind v3 + CSS variables. - Shared (
src/shared/types.ts) is the only place both processes import from. Keep it free of runtime imports from either side.
The browser ↔ main connection is intentionally a localhost HTTP API (Bun.serve on AGETOR_API_PORT, default 4317), not Electrobun's RPC. The API binds to 127.0.0.1 only and gates every route (except /health) on a per-launch random token generated in src/bun/server.ts:API_TOKEN. Both the port and the token are passed to the webview via #api=…&token=… on the window URL (hash fragment, not query string — the bundled views:// scheme handler treats anything after the scheme as a literal file path and would otherwise look for a file named mainview/index.html?api=…). src/mainview/lib/api.ts reads them at load and echoes back as Authorization: Bearer … on fetches and as ?token=… on the SSE URL (EventSource can't set headers). A site the user happens to visit can't read the token, so even with ACAO set permissively, drive-by CSRF can't drive an agent run.
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.
- today Changed · +1,117 tokens per session scan E → F d7a451432a0c
- 4d ago First seen · 264 lines · 25,072 tokens per session scan E 8696debac42a
agetor CLAUDE.md is an instructions file published in the GitHub repository alamops/agetor (57 stars, last pushed 2d ago), licensed MIT. It adds 26,189 tokens to every session, about $0.1309 per session on Opus 5. A static security scan graded it F with 5 findings (tells the agent never to refuse, downloads and executes remote code, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.