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 allemaar/open-skills --skill extract-signalgit clone --depth 1 https://github.com/allemaar/open-skillsWrote 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/allemaar/open-skills/extract-signal)<a href="https://agentmods.dev/skills/allemaar/open-skills/extract-signal"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/extract-signal/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/allemaar/open-skills/extract-signal"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/extract-signal.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.00221 | $0.02599 |
| Opus 5 | $0.00111 | $0.01300 |
| Sonnet 5 | $0.00044 | $0.00520 |
| Haiku 4.5 | $0.00022 | $0.00260 |
Grade A, and why
extract-signal 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 12d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/extract-signal
An elastic methodology for turning a noisy source surface into a vetted signal in the form the requester asked for, without contaminating the context that must stay clean. It is a goal + a toolkit + the judgment to compose techniques to fit the task — not a fixed pipeline. The work it does is determined by the context it is invoked with.
Structured execution spec:
protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the@STAMPdate.
The principle that motivates this skill
Context hygiene comes from RELOCATION, not TRUNCATION. Noisy work happens where noise is cheap — a spawned sub-agent's window, or this skill's own disposable window when it is itself a sub-agent. Only the signal reaches the place that must stay clean. The gathering area is never shrunk to fit an arbitrary size.
Inference & contracts (read the call, don't demand a form)
The skill infers its parameters from how it was invoked; explicit overrides are accepted but never required:
- What signal — the question to answer.
- What form — the output shape (see menu). Inferred from the ask ("as a risk-list", "is it ready?", "what are the options").
- Stakes — inferred from consequence; drives vetting depth.
- Mode & output — inferred per below.
Modes & output (inferred)
- Agentic (default — the normal call). extract-signal spawns a freshly-primed sub-agent that does the gather/vet/present and returns the signal. Relocation keeps the caller's window clean. Output returns to the caller (inline) unless a file is specified.
- In-session / new-session (it IS the agent). extract-signal works directly as the running agent; output inline by default, to a file if specified. (When it is itself a dispatched sub-agent, this is the same path: it works inline in its disposable window and does NOT spawn further sub-agents — depth-1 guardrail; the isolation already protects the caller.)
What ships with it
1 file 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.
- 12d ago First seen · 156 lines · 221 tokens per session scan A 47e226572035
extract-signal is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed yesterday), licensed Apache-2.0. It adds 221 tokens to every session and 2,599 once invoked, about $0.0011 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-30.
Other skills, from other repositories
polis-protocol
Set up and run a self-improving, multi-vendor AI agent team with the Polis Protocol — a markdown polis/ folder where each agent is a citizen with a capability card, tasks are contracts routed to whoever has the best track record by a learning router, settled work files lessons that compound into team memory, and…
media
Skill "media" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
_data
Skill "_data" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.