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 cembasaranoglu/crafting-system-claude --skill scheduled-scoringgit clone --depth 1 https://github.com/cembasaranoglu/crafting-system-claudeWrote 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/cembasaranoglu/crafting-system-claude/scheduled-scoring)<a href="https://agentmods.dev/skills/cembasaranoglu/crafting-system-claude/scheduled-scoring"><img src="https://agentmods.dev/badge/skills/cembasaranoglu/crafting-system-claude/scheduled-scoring/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/cembasaranoglu/crafting-system-claude/scheduled-scoring"><img src="https://agentmods.dev/badge/skills/cembasaranoglu/crafting-system-claude/scheduled-scoring.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.00094 | $0.00459 |
| Opus 5 | $0.00047 | $0.00230 |
| Sonnet 5 | $0.00019 | $0.00092 |
| Haiku 4.5 | $0.00009 | $0.00046 |
Grade A, and why
scheduled-scoring 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 6d 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.
What it actually says
Scheduled Scoring
Apply the boundary first: CI measures, Claude interprets. Do not run scanners or clone target repos inside a scheduled task; that work belongs in GitHub Actions or GitLab Pipelines.
The full operating contract — score catalog, schedule routing matrix, cadence, weighted profiles, and output schema — is in references/:
163_scheduled_scoring_system.md— primary promptscheduled_scoring_policy.yaml— weighted profiles, bucket membership, routing matrix, hard rulesscheduled_run_report.schema.yaml— output schema (every run must conform)adr-0005-scheduled-scoring-boundary.md— boundary rationale
Workflow:
- Identify the surface (trigger / interpret / summarize). Ask once if unclear.
- Confirm required inputs (repo identity, CI artifacts, optional previous report, optional profile).
- If inputs are missing, return a
minimum_input_requestinstead of guessing. - Parse the provided artifacts and map findings into the score catalog.
- For any score without an artifact, set
not_runwith a reason — no silent zeros. - Compute the weighted total per the active profile (default:
standard). - If a previous report is provided, compute trend (
degraded_areas,improved_areas,delta). - Produce
recommended_actionsinimmediate,this_week,later, each linked to evidence. - Validate the output against the run-report schema.
Hard stops:
- Apparent secret in evidence -> stop, follow secret-aware credential handling.
- Recommended action implies destructive change -> escalate for human approval.
- Request asks Claude to run scanners directly -> refuse and redirect to CI.
What ships with it
4 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.
- 6d ago First seen · 34 lines · 94 tokens per session scan A 602ef85ee93b
scheduled-scoring is a skill published in the GitHub repository cembasaranoglu/crafting-system-claude (5 stars, last pushed 4mo ago), licensed MIT. It adds 94 tokens to every session and 459 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.