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/1broseidon/ketch/agents-mdgit clone --depth 1 https://github.com/1broseidon/ketchWrote 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/1broseidon/ketch/agents-md)<a href="https://agentmods.dev/instructions/1broseidon/ketch/agents-md"><img src="https://agentmods.dev/badge/instructions/1broseidon/ketch/agents-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.03278 | $0.03278 |
| Opus 5 | $0.01639 | $0.01639 |
| Sonnet 5 | $0.00656 | $0.00656 |
| Haiku 4.5 | $0.00328 | $0.00328 |
Grade A, and why
ketch AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -L https://example.com | ketch extract # piped HTML → markdown (no fetch) How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ketch — Architecture
Fast, stateless CLI for agentic web search and scrape.
Module Layout
main.go Thin entry point → cmd.Execute()
cmd/
root.go Cobra root, global flag (--json)
search.go Search command: query → results, optional --scrape
scrape.go Scrape command: URLs → markdown, concurrent batch
extract.go Extract command: piped HTML → markdown (no fetch/cache/browser)
crawl.go Crawl command: BFS/sitemap crawl with streaming output
crawl_bg.go Background crawl: status, stop subcommands, worker mode
code.go Code search command: query → snippet results, --lang qualifier
docs.go Docs search command: query → docs/snippet results, --library, --resolve
config.go Config command: discovery, init, set, path
cache.go Cache command: stats, clear
browser.go Browser command: install, status
doctor.go Doctor command: report formatting + exit-code gating over doctor.Run
mcp.go MCP command: `mcp serve` runs the MCP server over stdio
proc_unix.go Unix process management (detach, signals)
proc_windows.go Windows process management stub
search/ Searcher interface + Brave/DDG/SearXNG/EXA/Firecrawl/Keenable/Tavily/Parallel/SerpBase backends; NewFromConfig owns the backend switch for cmd/ and mcp/. multi.go adds federated --multi search (RRF fusion, NewMultiFromConfig), canonical.go the URL dedup keys
code/ code.Searcher interface + GrepApp/Sourcegraph/GitHub backends; NewFromConfig owns the backend switch
docs/ docs.Searcher interface + Context7 backend (FTS5 local is an unimplemented stub); NewFromConfig owns the backend switch
mcp/ MCP server (search/code/docs/scrape/crawl tools; the mcp_tools config key is an allowlist over the published set) over the go-sdk mcp package; Server struct holds the shared scraper + cache, tools call the same NewFromConfig constructors as the CLI
scrape/ HTTP fetch + Page type, JS detection fallback, Rod browser; pipeline.go has the cache-aware scrape pipeline (CachedScrape*, ScrapeSelector, FetchLLMSTxt) shared by cmd/ and mcp/
extract/ readability + html-to-markdown pipeline, JS shell detection (Detector: built-in + config spa_markers, modern hydration/streaming frameworks)
crawl/ BFS crawler, work queue + worker pool, background status
cookies/ Netscape cookies.txt jar loader + RFC 6265 domain/path matching (Jar.For); nil-safe, values never logged
config/ JSON config loading/saving (~/.config/ketch/)
doctor/ Health checks: concurrent read-only probes per backend + browser + cache, status classification (ok/no_key/unreachable/misconfigured/skipped)
cache/ TTL page cache (Store interface, BBoltStore backend)
httpx/ Shared tuned *http.Transport for all HTTP backends
updatecheck/ "new release available" probe + throttled stderr hint
site/ VitePress documentation site (deployed to gh-pages)
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 · +107 tokens per session 248a81f5fc36
- 5d ago First seen · 150 lines · 3,171 tokens per session scan A cf2cd7a805af
ketch AGENTS.md is an instructions file published in the GitHub repository 1broseidon/ketch (538 stars, last pushed 4d ago), licensed MIT. It adds 3,278 tokens to every session, about $0.0164 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
Scrapegraph-ai AGENTS.md
Instructions for ScrapeGraphAI/Scrapegraph-ai, covering agents.md, 1. golden rule: everything goes to pre/beta, 1. always start from an up-to-date pre/beta, 2. commit your work and 3. push and open the pr against pre/beta.
rayobrowse AGENTS.md
Instructions for rayobyte-data/rayobrowse, covering agents.md, what this project is, prerequisites, local setup and primary usage pattern.
cs CLAUDE.md
Claude Code instructions for boyter/cs, covering claude.md, project overview, build & test commands, architecture and query pipeline (pkg/search/).
Xapiand AGENTS.md
Instructions for Kronuz/Xapiand, covering agents.md — working in the xapiand codebase, first, the big split: own code vs. vendored, where things live, build & toggles and verifying changes end-to-end (the docs are a test suite).
AutomatiQ AGENTS.md
AGENTS.md instructions for StoneSteel27/AutomatiQ, covering agent guidelines, project map, daily commands, doctrine and config.
servo-fetch AGENTS.md
AGENTS.md instructions for konippi/servo-fetch, covering agents.md, project overview, setup and commands, code conventions and rust style.