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/jumplink/troedler/agents-mdgit clone --depth 1 https://github.com/JumpLink/troedlerWrote 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/jumplink/troedler/agents-md)<a href="https://agentmods.dev/instructions/jumplink/troedler/agents-md"><img src="https://agentmods.dev/badge/instructions/jumplink/troedler/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.04004 | $0.04004 |
| Opus 5 | $0.02002 | $0.02002 |
| Sonnet 5 | $0.00801 | $0.00801 |
| Haiku 4.5 | $0.00400 | $0.00400 |
Grade A, and why
troedler AGENTS.md 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — troedler
Operating guide for AI agents in the troedler repo. Follows the agents.md convention; human overview in README.md. This repo is a submodule of werkstatt, whose AGENTS.md carries the broader workspace rules — this file is the troedler-specific layer and wins where they differ.
What this is
Search several second-hand marketplaces with one query, as a CLI and an MCP server. A TypeScript
monorepo that runs on GJS via gjsify (not Node), following the postbote pattern: pure-TS
packages/* plus one app workspace that carries the gjsify toolchain and picks a frontend at
the yargs entrypoint. A native GNOME/Adwaita GUI is planned and the seams are already cut for it.
v1 is read-only towards every marketplace. No account, no login, no listing, no bidding, no messaging. It reads what is public and tells you what it found.
Leitplanken (hard rules)
These are not style. Each one is the reason some part of the code looks the way it does, and removing one silently changes what this project is.
|Local, per user, never central. No hosted crawler, no shared index, no server endpoint, no
pooling of other people's searches. That is the line between local multi-marketplace software
(BGH I ZR 159/10, permitted) and a hosted meta-search engine (CJEU C-202/12 Innoweb,
prohibited). It is why the MCP server speaks stdio and there is no HTTP transport.
|An official API beats HTML, always. Where a marketplace offers one, the HTML path is not
implemented at all — not as a fallback, not "for later".
|robots.txt is a gate, not a hint. Parsed per host, cached, checked before every request in
@troedler/http. Crawl-delay honoured, otherwise ≥2 s and one connection per host. Never build a
URL the gate would refuse: a disallowed filter path is not a feature that unfortunately blocks, it
is the thing the operator forbade.
|Never logged in. No cookie jar, no session handling, no account. Without registration there
is no contract of use to breach; with a login, every clause applies.
|Never circumvent. No browser user-agent spoofing, no captcha/Cloudflare/Akamai/TLS-fingerprint
bypass, no proxy rotation, no retry with altered headers. 403 and 429 end the attempt with a
plain-language error. A refusal is a decision, not a hiccup.
|Never reverse-engineered credentials. No tokens or keys extracted from apps or binaries, no
private endpoints behind auth. This is the one line here with criminal exposure (§ 202a StGB,
Modern-Solution line of cases through BVerfG 2025) and it is not close to the edge.
|Cache is query-scoped TTL, never a mirror. Only queries a user actually made. No paging
through a catalogue, no building a local picture of a market. eBay listing data: ≤6 h by licence.
|Personal data is filtered while parsing, not cleaned up later. No seller names or ids, no
profiles, no histories; phone numbers and e-mail addresses stripped from free text at the parser.
Images are URLs — never downloaded, never rehosted.
|Honest user agent, troedler/<version> (+repo-url), with a reachable contact. No spoofing.
It is also how an operator who objects can reach us at all.
|OPT_OUT_HOSTS in @troedler/compliance is binding. A host that objects is refused by the
gate and removed in the next release.
|A new source means a source record first. docs/quellen/<host>.md — robots.txt findings,
the terms clause quoted, whether an API exists, bot protection, date checked — then an entry in
SOURCES, then the adapter. No adapter without one.
|Fixtures are synthetic. Never commit a real listing, page capture, or database. Measure
against live pages locally; commit only HTML you wrote yourself.
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.
- 3d ago First seen · 232 lines · 4,004 tokens per session scan A 667178410976
troedler AGENTS.md is an instructions file published in the GitHub repository JumpLink/troedler (0 stars, last pushed 10d ago), licensed MIT. It adds 4,004 tokens to every session, about $0.0200 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-31.
Other instructions, from other repositories
ebay-mcp AGENTS.md
Instructions for YosefHayim/ebay-mcp, covering agents.md, what this is, instruction sources, validation commands and module map (src/).
taiwan-ecommerce-toolkit CLAUDE.md
Instructions for Moksa1123/taiwan-ecommerce-toolkit, covering claude.md, project overview, available scripts, test api connectivity and validate invoice data.
sparrowhawk AGENTS.md
AGENTS.md instructions for bacpop/sparrowhawk, covering agents.md — sparrowhawk, what this is, getting a working checkout, two facts that will otherwise cost you an hour and layout.
rubydex AGENTS.md
AGENTS.md instructions for Shopify/rubydex, covering instructions, project overview, documentation, ruby gem and structure.
GooFish-AIMonitor AGENTS.md
Instructions for tristanwqy/GooFish-AIMonitor, covering agents.md — 给 ai 协作者的工程指南, 黄金规则(先读这条), 验证命令(完成前必跑), 代码地图 and 数据模型要点.
tracepass-mcp-server CLAUDE.md
Claude Code instructions for malinoto/tracepass-mcp-server, covering tracepass-mcp-server, architecture (the one rule everything serves), tool/result conventions to preserve, releasing (three independent channels) and before changing anything.