Borrowing it
Nothing to install: this file belongs to sassoftware/sas-score-mcp-serverjs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sassoftware/sas-score-mcp-serverjs/main/.skills/skills/read-strategy/SKILL.mdgit 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/read-strategy)<a href="https://agentmods.dev/skills/sassoftware/sas-score-mcp-serverjs/read-strategy"><img src="https://agentmods.dev/badge/skills/sassoftware/sas-score-mcp-serverjs/read-strategy.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.1 | $0.00027 | $0.00869 |
| Opus 5 | $0.00014 | $0.00434 |
| Sonnet 5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
read-strategy 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read Table Strategy
Mandatory two-step sequence — never skip or reorder
Step 1 and Step 2 are required for every read request. Step 2 must never run before Step 1 succeeds.
Step 1 — Verify the table exists and resolve its server (REQUIRED)
GATE:
Do not check for the existence of the library separately. Follow the workflow below. The sas-score-find-table tool will check for the existence of the table in the specified library and server, which implicitly verifies the library as well.
Workflow to read a table
Step 1 — Verify the table exists and resolve its server (REQUIRED)
- Call
sas-score-find-table({ lib, name: table, server: "cas" })- ✅ Found → confirmed
lib= lib as given, confirmedserver="cas"→ go to Step 2 - ❌ Not found → call
sas-score-find-table({ lib: lib.toUpperCase(), name: table, server: "sas" })- ✅ Found → confirmed
lib= uppercased lib, confirmedserver="sas"→ go to Step 2 - ❌ Not found in either → stop. Tell the user the table was not found.
- ✅ Found → confirmed
- ✅ Found → confirmed
Step 2 — Read the table
Use the confirmed lib and server from Step 1. Never guess or default the server.
Use sas-score-read-table for all row reads, including filtered reads with a WHERE clause.
Use sas-score-sas-query only when the request requires SQL aggregation (COUNT, SUM, AVG, MIN, MAX), GROUP BY, JOIN, or computed columns. A WHERE clause alone is not a reason to use sas-query.
Read Table (sas-score-read-table)
When: raw rows, filtered rows, browsing — anything that is not an aggregation or join.
Parsing row count from user input:
| User says | start | limit |
|---|---|---|
| "first N rows/records" | 1 | N |
| "top N rows" | 1 | N |
| "N rows" / "N records" | 1 | N |
| "rows N to M" | N | M−N+1 |
| "starting from row N" | N | 10 |
| (not specified) | 1 | 10 |
"first" always means start at row 1 and return N rows. It is never a row offset.
Dotted format: "lib.table" → lib: "lib", table: "table" (split on first dot).
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.
- 8d ago First seen · 88 lines · 27 tokens per session scan A 0a9ce6c99c3e
read-strategy 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 27 tokens to every session and 869 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.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…