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 skills add saski/arnesto --skill madrid-avisosgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/madrid-avisos)<a href="https://agentmods.dev/skills/saski/arnesto/madrid-avisos"><img src="https://agentmods.dev/badge/skills/saski/arnesto/madrid-avisos/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/skills/saski/arnesto/madrid-avisos"><img src="https://agentmods.dev/badge/skills/saski/arnesto/madrid-avisos.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.00063 | $0.01370 |
| Opus 5.5 | $0.00025 | $0.00548 |
| Sonnet 5.5 | $0.00013 | $0.00274 |
| Haiku 4.5 | $0.00006 | $0.00137 |
Grade A, and why
madrid-avisos 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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Madrid Avisos
Turn the user's observations into an accurate municipal report. Speak Spanish unless the user requests another language. The portal is Avisos Madrid.
Choose the available mode
- With an interactive browser, inspect the live portal and carry the authorized workflow through to its visible result. Use the host's supported browser tools.
- With only search, HTTP extraction, or no browser, prepare a paste-ready draft and a precise handoff. These capabilities cannot submit this JavaScript form.
- A verified integration may replace browser steps only if its documented capabilities cover the operation. Do not invent an API from frontend URLs.
Read portal.md when interacting with the website. Read sessions.md when reusing or establishing access, and runtimes.md only for installation or capability issues. Loading this skill grants no additional permissions or browser access.
Gather and draft
- Extract the problem, exact incident location, and requested action from the conversation. Reuse information already given. Ask a focused question only for missing details that prevent an accurate report. A street number, intersection, or identifiable landmark may resolve a vague location; do not infer the incident location from the user's home, IP, or a photo's metadata.
- Distinguish AVISO (a problem with an existing street element) from PETICIÓN (a requested new element). Check that the issue concerns Madrid city. For immediate danger, direct the user to emergency services. For a different municipality or a formal appeal, identify the appropriate channel instead of treating this portal as a substitute.
- Write a concise Spanish description: observable problem, precise location, reported duration or impact if supplied, and the requested intervention. Do not invent dates, dimensions, causes, danger, ownership, or responsibility. Preserve uncertainty and distinguish an observation from an allegation.
- Photos are optional. Use only attachments selected by the user for this report. Do not generate evidence or upload unrelated files. Identify unnecessary faces, identifying details, or private data before upload; offer omission or a redacted copy and preserve originals. Never place contact details, credentials, identity numbers, or banking details in the public description.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 113 lines · 63 tokens per session scan A 1bcb367784b0
madrid-avisos is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed yesterday), licensed Unlicense. It adds 63 tokens to every session and 1,370 once invoked, about $0.0003 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-10-08.
Other skills, from other repositories
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.