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 sassoftware/sas-score-mcp-serverjs --skill sas-score-find-library-servergit 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/sas-score-find-library-server)<a href="https://agentmods.dev/skills/sassoftware/sas-score-mcp-serverjs/sas-score-find-library-server"><img src="https://agentmods.dev/badge/skills/sassoftware/sas-score-mcp-serverjs/sas-score-find-library-server/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/sassoftware/sas-score-mcp-serverjs/sas-score-find-library-server"><img src="https://agentmods.dev/badge/skills/sassoftware/sas-score-mcp-serverjs/sas-score-find-library-server.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.00062 | $0.00530 |
| Opus 5.5 | $0.00025 | $0.00212 |
| Sonnet 5.5 | $0.00012 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
sas-score-find-library-server 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 9d 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
Find Library Server
Purpose: Verify a library exists and determine whether it lives in CAS or SAS.
Tool: sas-score-find-library({ name, server })
Workflow
-
Call
sas-score-find-library({ name: "<lib>", server: "cas" })- ✅ Found → return
{ lib: "<lib>", server: "cas" } - ❌ Not found → go to step 2
- ✅ Found → return
-
Look in SAS
- Uppercase the library name
- call
sas-score-find-library({ name: "<LIB_UPPERCASED>", server: "sas" })- ✅ Found → return
{ lib: "<LIB_UPPERCASED>", server: "sas" } - ❌ Not found → library does not exist; stop and report not found to the user
- ✅ Found → return
Known Library Hints (skip searching if known)
Use these to skip the two-step search when the server is already deterministic:
| Library (case-insensitive) | Server |
|---|---|
| Casuser, Formats, ModelPerformanceData, Models, Public, Samples, SystemData | "cas" (check CAS only) |
| MAPS, MAPSGFK, MAPSSAS, SASDQREF, SASHELP, SASUSER, WORK | "sas" (check SAS only, uppercase lib) |
| Unknown | Try CAS first; if not found, try SAS with uppercased lib |
Output
Always return the confirmed resolved values to the caller:
| Field | Value |
|---|---|
lib |
Confirmed library name (may be uppercased for SAS) |
server |
"cas" or "sas" |
Error Handling
- Not found in either server → confirm spelling with the user and offer to list available libraries.
- Do not fall back to listing libraries as a substitute for verification — they serve different purposes.
Important Constraints
- Never use
list-*tools for library verification — use onlysas-score-find-library. - This skill verifies libraries only. To verify a table, use
sas-score-find-tabledirectly (it validates the library implicitly).
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.
- 9d ago First seen · 65 lines · 62 tokens per session scan A 41611a9e0efd
sas-score-find-library-server is a skill published in the GitHub repository sassoftware/sas-score-mcp-serverjs (1 stars, last pushed 9d ago), licensed Apache-2.0. It adds 62 tokens to every session and 530 once invoked, about $0.0002 per session on Opus 5.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-10-10.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…