score-importance

score-importance is a skill for Claude Code from jezweb/vite-flare-starter. It costs 30 tokens per session (573 once invoked), scanned A, original, MIT.

A rule for assigning high, medium, or low importance to items added to an inbox. It defines how urgently an item needs attention.

In plain words
What is it for?
Use it to classify failures, security alerts, leads, stuck work, reminders, trends, and other inbox items by how quickly someone should act.
Why use it?
It keeps different routines consistent, so the same type of task receives the same priority instead of confusing users.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Good fit Use it to classify failures, security alerts, leads, stuck work, reminders, trends, and other inbox items by how quickly someone should act.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jezweb/vite-flare-starter/score-importance
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 jezweb/vite-flare-starter --skill score-importance
Clone the repo
git clone --depth 1 https://github.com/jezweb/vite-flare-starter

Made for: Claude Code.

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 score-importance

README.md
[![agentmods](https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/score-importance/github.svg)](https://agentmods.dev/skills/jezweb/vite-flare-starter/score-importance)
Your own site
<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/score-importance"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/score-importance/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 score-importance

Your own site · 80×15
<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/score-importance"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/score-importance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 573 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00030 $0.00573
Opus 5 $0.00015 $0.00287
Sonnet 5 $0.00006 $0.00115
Haiku 4.5 $0.00003 $0.00057

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

Security

Grade A, and why

score-importance 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/score-importance/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Score Importance

Purpose

inbox_add accepts an importance field — high, medium, or low. Without consistency, what one routine calls "high" another calls "medium" and the user stops trusting the field.

This skill defines what each level means so all your routines agree.

Definitions

high

Action is needed within the day. If the user ignores it, something will break or get worse.

Examples:

  • Backup failed. Quota exceeded. Auth expired on a connector the user relies on.
  • A new high-value lead replied; a hot conversation needs follow-up by EOD.
  • Cost overrun on a paid integration.
  • Security signal: unfamiliar login, unusual API rate.

medium

Action is helpful within the week. Not blocking, but skipping has a cost.

Examples:

  • Stuck items (tickets, leads, drafts) older than the user's threshold.
  • A meeting summary the user might want to skim before tomorrow.
  • A summary of activity the user usually checks daily but missed today.
  • A trend (search volume, engagement) worth knowing about.

low

FYI. Skipping has no cost. The user is happy to know but won't act.

Examples:

  • A YouTube/article summary; "the X talk you bookmarked is now public".
  • Counters: "you sent 14 messages today, your average is 11".
  • Routine status: "all 12 sites checked, all healthy" (when the user wants to see proof of work).

Heuristics

Signal Suggests
Time-bound (deadline, expiry) high
Money-bound (cost, revenue) high or medium
Failure / regression high
Volume / count change medium or low
New content (article, video, message) low (unless from a key relationship)
"Should I look at this?" — user-paced medium or low

Confidence

Pair importance with confidence (0..1). High confidence + medium importance is more actionable than low confidence + high importance. If you're not sure something matters, lean low + add a reasoning line so the user can confirm.

Anti-patterns

  • Don't mark routine work high to get the user's attention. The user disables routines that cry wolf.
  • Don't use low for things you secretly think are high — that's still crying wolf, just inverted.
  • Don't fill importance if you genuinely don't know. Leave it null and let the user filter.

Read the full file on GitHub · 66 lines

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 · 66 lines · 30 tokens per session scan A b03cd3af6a30

Subscribe to this mod's changes

score-importance is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 15d ago), licensed MIT. It adds 30 tokens to every session and 573 once invoked, about $0.0002 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.