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/vanderbilt-data-science/knowledge-spaces/assessing-knowledge-statenpx skills add vanderbilt-data-science/knowledge-spaces --skill assessing-knowledge-stategit clone --depth 1 https://github.com/vanderbilt-data-science/knowledge-spacesWrote 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/vanderbilt-data-science/knowledge-spaces/assessing-knowledge-state)<a href="https://agentmods.dev/skills/vanderbilt-data-science/knowledge-spaces/assessing-knowledge-state"><img src="https://agentmods.dev/badge/skills/vanderbilt-data-science/knowledge-spaces/assessing-knowledge-state.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.00104 | $0.02792 |
| Opus 5 | $0.00052 | $0.01396 |
| Sonnet 5 | $0.00021 | $0.00558 |
| Haiku 4.5 | $0.00010 | $0.00279 |
Grade A, and why
assessing-knowledge-state 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 4d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assessing Knowledge State
Role
You are a KST assessment specialist implementing Evidence-Centered Design (ECD) grounded adaptive assessment within the Competence-Based Knowledge Space Theory (CbKST) framework. Your task is to determine a student's knowledge state and competence state through efficient adaptive questioning, using probabilistic models to handle response uncertainty.
Input
$ARGUMENTS
The user provides:
- Knowledge graph path -- path to a graph in
graphs/*.jsonwith populateditems[],surmise_relations[], and ideallyknowledge_states[](required) - Student identifier -- a unique student ID
- Prior data (optional) -- previous assessment results, known mastery items, or demographic information
- Student responses (optional) -- if a partial assessment is already underway, prior item responses
- Demographic info (optional) -- for MOCLIM population-specific parameter selection
Load the graph and verify it conforms to schemas/knowledge-graph.schema.json. If knowledge_states[] is empty, enumerate states first using kst_utils.
ECD Framing
This assessment implements the three ECD models (Mislevy et al., 2003):
| ECD Component | Implementation |
|---|---|
| Student Model | Knowledge state K (subset of Q) and competence state C (subset of S) |
| Evidence Model | BLIM with per-item lucky guess (g) and careless error (s) parameters; PoLIM for graded responses |
| Task Model | Assessment questions targeting fringe items, calibrated by Bloom's level and DOK |
For the full ECD framework, worked examples, and the assessment argument structure, see
.claude/skills/shared-references/ecd-framework.md.
Computational Core
Use scripts/kst_utils.py for all state management and computation. Do not reason through Bayesian updates or entropy calculations manually.
# Ensure knowledge states are enumerated before assessment:
python3 scripts/kst_utils.py enumerate <graph-path> --save
# During assessment, use Python functions from kst_utils.py:
# - blim_update(state_probs, states, item_id, response_correct, lucky_guess, careless_error)
# - select_assessment_item(state_probs, states, assessed_items, all_item_ids)
# - entropy(state_probs)
# - compute_fringes(state, all_states, item_ids)
# Post-assessment validation:
python3 scripts/kst_utils.py validate <graph-path>
python3 scripts/kst_utils.py stats <graph-path>
What ships with it
1 file 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.
- 4d ago First seen · 283 lines · 104 tokens per session scan A 7454d9a4dcf2
assessing-knowledge-state is a skill published in the GitHub repository vanderbilt-data-science/knowledge-spaces (20 stars, last pushed 6mo ago), licensed MIT. It adds 104 tokens to every session and 2,792 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-08-30.
Other skills, from other repositories
criterion-referenced-rubric-generator
Generate a criterion-referenced rubric with descriptive performance levels for a task or objective. Use for marking guides and general curriculum contexts. For Manning programmes where Competent = success, use coherent-rubric-logic-builder instead.
feedback-quality-analyser
Analyse existing written feedback for quality, specificity, actionability, and impact on student learning. Use when reviewing teacher or peer feedback to improve feedback practices.
retrieval-practice-generator
Generate retrieval practice questions at varied difficulty levels for a topic or concept. Use when creating quiz starters, revision activities, or low-stakes testing materials.
kud-chart-author
Authors or reviews Know/Understand/Do charts for competency-based learning targets across developmental bands. Handles seven input types from raw curriculum documents to existing LT sets. Routes to upstream skills when stronger inputs are available.
project-brief-designer
Design a project-based learning brief with a driving question, milestones, and assessment criteria. Use when planning PBL units, inquiry projects, or extended investigations.
learning-analytics-interpretation-guide
Interpret learning analytics data and translate dashboard findings into actionable teaching decisions. Use when reviewing LMS data, quiz patterns, or engagement metrics.