Filter Signals

Filter Signals is a skill for Claude Code, Codex from YuiZhou/dayarc-agent. It costs 12 tokens per session (226 once invoked), scanned A, original, MIT.

A filter that scores incoming emails, Teams messages, and GitHub notifications against a user's profile. It keeps matching signals and drops low-relevance ones.

In plain words
What is it for?
Use it to rank and select up to ten relevant signals, with a short reason explaining each one.
Why use it?
It reduces noise in incoming notifications by focusing attention on saved items, direct mentions, assignments, reviews, and profile-related topics.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to rank and select up to ten relevant signals, with a short reason explaining each one.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yuizhou/dayarc-agent/dayarc-filter-signals
Install

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.

Any agent
npx skills add YuiZhou/dayarc-agent --skill dayarc-filter-signals
Clone the repo
git clone --depth 1 https://github.com/YuiZhou/dayarc-agent

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for Filter Signals

README.md
[![agentmods](https://agentmods.dev/badge/skills/yuizhou/dayarc-agent/dayarc-filter-signals/github.svg)](https://agentmods.dev/skills/yuizhou/dayarc-agent/dayarc-filter-signals)
Your own site
<a href="https://agentmods.dev/skills/yuizhou/dayarc-agent/dayarc-filter-signals"><img src="https://agentmods.dev/badge/skills/yuizhou/dayarc-agent/dayarc-filter-signals/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.

agentmods 80×15 button for Filter Signals

Your own site · 80×15
<a href="https://agentmods.dev/skills/yuizhou/dayarc-agent/dayarc-filter-signals"><img src="https://agentmods.dev/badge/skills/yuizhou/dayarc-agent/dayarc-filter-signals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 226 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00226
Opus 5 $0.00006 $0.00113
Sonnet 5 $0.00002 $0.00045
Haiku 4.5 $0.00001 $0.00023

Measured 10d ago against content hash cff91f4087bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

Filter Signals 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 10d 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.

skills/dayarc-filter-signals/SKILL.md · 27 lines

What it actually says

Input

Incoming signals (new emails, Teams messages, GitHub notifications), user profile.

Output (JSON)

{
  "signals": [{
    "description": "Email from Jane about cost optimization review",
    "source_breadcrumb": "Outlook: Re: Cost optimization review",
    "relevance": 0.9,
    "pass_reason": "matches focus_area: cost optimization"
  }]
}

Instructions

  1. Auto-pass (relevance=1.0): flagged, saved, direct @mention, GitHub review_requested, GitHub assigned. pass_reason = "flagged"/"saved"/"direct mention"/"review requested"/"assigned".
  2. Others: score 0-1 based on overlap with profile's focus_areas, key_contacts, active_threads.
  3. Include if relevance ≥ 0.4. Write pass_reason explaining which profile element matched.
  4. Below threshold: silently drop.
  5. Max 10 signals. Sort by relevance descending.
Changes

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.

  1. 10d ago First seen · 27 lines · 12 tokens per session scan A cff91f4087bb

Subscribe to this mod's changes

Filter Signals is a skill published in the GitHub repository YuiZhou/dayarc-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 12 tokens to every session and 226 once invoked, about $0.0001 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.