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 skills/agentproto/ts/leboncoinnpx skills add agentproto/ts --skill leboncoingit clone --depth 1 https://github.com/agentproto/tsWrote 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/skills/agentproto/ts/leboncoin)<a href="https://agentmods.dev/skills/agentproto/ts/leboncoin"><img src="https://agentmods.dev/badge/skills/agentproto/ts/leboncoin.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.00055 | $0.00922 |
| Opus 5 | $0.00028 | $0.00461 |
| Sonnet 5 | $0.00011 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade B, and why
leboncoin scanned grade B 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 4d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const r = await fetch("https://api.leboncoin.fr/finder/search", { method: "POST", How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Leboncoin — recon plan (FR marketplace)
Not a social graph — a marketplace: the "nodes" are Ads and Sellers, the edges are seller↔listings, category/location facets, and messaging. Same recon method (find the API → auth from cookies → typed queries → playbooks).
Internal API: https://api.leboncoin.fr/... (the web app calls it
directly):
- Search:
POST https://api.leboncoin.fr/finder/search— JSON body withfilters(category, location {region/department/city}, keywords, price range, attributes),limit,offset,sort_by. Returnsads[]+ facets. - Ad detail:
GET https://api.leboncoin.fr/api/adview/v1/public/<listId>(or the listing page hydration) — price, description, images, attributes, seller. - Seller: the seller's other listings (search by
owner/user_id), pro/private, ratings. - Messaging: the conversation API (login required).
Auth (from the page)
api_keyheader — a public web key Leboncoin's JS sends on every call (capture from a request header).- cookies ride same-origin, including the
datadomecookie — Leboncoin is behind DataDome anti-bot (like a WAF). Because we run in the REAL browsing session, the validdatadomecookie is already present → page-context fetch passes. (This is the gate, analogous to TikTok's signing.)
In-page fetch:
async body => {
const r = await fetch("https://api.leboncoin.fr/finder/search", {
method: "POST",
headers: {
"content-type": "application/json",
api_key: "<captured web api_key>",
},
body: JSON.stringify(body),
})
return await r.json()
}
Entity model
Ad{ list_id, subject, body, price, category, location{city,zipcode,lat,lng}, images[], attributes[], owner:Seller, index_date }
· Seller{ user_id, name, type: private|pro, siret?, no_of_ads, ratings? } ·
Category{ id, name }.
Recipes (read-first; writes gated)
- Search listings:
finder/searchwith filters → ads (price, location, seller). - Ad detail:
adview→ full ad + seller + images. - Seller's listings: search filtered by the owner/user_id → their inventory (the "persona" of a seller = their listings + pricing + activity).
- Market scan / price graph: search a category+area → aggregate prices, freshness, sellers → a market view (the marketplace analog of the social graph).
- Discovery → outreach: find matching ads → (gated) message the seller.
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.
- 4d ago First seen · 89 lines · 55 tokens per session scan B 44d94f99fe48
leboncoin is a skill published in the GitHub repository agentproto/ts (5 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 922 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
p5.js
Production pipeline for interactive and generative visual art using p5.js. Creates browser-based sketches, generative art, data visualizations, interactive experiences, 3D scenes, audio-reactive visuals, and motion graphics — exported as HTML, PNG, GIF, MP4, or SVG. Covers: 2D/3D rendering, noise and particle systems…
docs-link-checker
Crawl a documentation site's own navigation and report broken links and empty pages.
form-filler
Fill and submit a web form from provided values, then verify the confirmation.
pretext
Use when building creative browser demos with @chenglou/pretext — DOM-free text layout for ASCII art, typographic flow around obstacles, text-as-geometry games, kinetic typography, and text-powered generative art. Produces single-file HTML demos by default.
p5js
Use when users request: p5.js sketches, creative coding, generative art, interactive visualizations, canvas animations, browser-based visual art, data viz, shader effects, or any p5.js project.
Google Workspace
Handle Google Docs, Sheets, Drive, and related Workspace tasks through the narrowest available API or browser workflow.