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 agentmods add skills/sassoftware/sas-score-mcp-serverjs/score-programnpx skills add sassoftware/sas-score-mcp-serverjs --skill score-programgit clone --depth 1 https://github.com/sassoftware/sas-score-mcp-serverjsWrote 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/sassoftware/sas-score-mcp-serverjs/score-program)<a href="https://agentmods.dev/skills/sassoftware/sas-score-mcp-serverjs/score-program"><img src="https://agentmods.dev/badge/skills/sassoftware/sas-score-mcp-serverjs/score-program.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.00473 |
| Opus 5 | $0.00039 | $0.00236 |
| Sonnet 5 | $0.00015 | $0.00095 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
score-program 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 3d 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
Score SAS Program / Macro
When to use this skill
-
When the user wants to score a SAS program (
.sas), -
User references a SAS macro by name (Macro)
For CAS programs (
.casl) or CAS model tables, use the score-cas skill instead.
Tools
| Type | Verify | Score |
|---|---|---|
| Program | (no pre-check) | sas-score-program-score |
| Macro | (no pre-check) | sas-score-macro-score |
Inline Scenario Scoring
Program (.sas):
- Score directly:
sas-score-program-score({ src, scenario, folder, output, limit })
Macro:
- Score directly:
sas-score-macro-score({ macro, scenario })
No verification step for any program type — they are executed directly.
Table Row Scoring
Parsing row count:
| User says | start | limit |
|---|---|---|
| "score the first N rows from lib.table" | 1 | N |
| "score N rows from lib.table" | 1 | N |
| (count not specified) | 1 | 10 |
Flow:
- Read table → use read-strategy skill
- Score each row — tools accept a single row; loop over rows calling the tool for each
- Return rows with predictions appended
- Cap batch at 10 rows by default; ask user before proceeding with larger batches
Error Handling
| Error | Action |
|---|---|
| Program source not found | Confirm src path or folder with user |
| Table not found | Confirm table name and library |
| Empty table | Ask user to adjust filter or confirm criteria |
| Scoring failure | Return tool error verbatim |
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.
- 3d ago First seen · 60 lines · 77 tokens per session scan A 0a387227d6ec
score-program is a skill published in the GitHub repository sassoftware/sas-score-mcp-serverjs (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 473 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…