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 panaversity/ksor --skill intake-interviewgit clone --depth 1 https://github.com/panaversity/ksorWrote 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/panaversity/ksor/intake-interview)<a href="https://agentmods.dev/skills/panaversity/ksor/intake-interview"><img src="https://agentmods.dev/badge/skills/panaversity/ksor/intake-interview/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/panaversity/ksor/intake-interview"><img src="https://agentmods.dev/badge/skills/panaversity/ksor/intake-interview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.02355 |
| Opus 5.5 | $0.00034 | $0.00942 |
| Sonnet 5.5 | $0.00017 | $0.00471 |
| Haiku 4.5 | $0.00008 | $0.00235 |
Grade A, and why
intake-interview 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 1mo 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intake interview
instance.md is the identity of this Knowledge System of Record, and its
prose IS the agent surface's system prompt (ksor serve wires it into the MCP
server's instructions). Do not draft it from guesses — interview the owner, one
question at a time, and write down what they actually say.
Ask THREE questions, one at a time
Ask them in the OWNER's words, not this project's. The vocabulary on this page — record, corpus, abstention, governance act — is precise and it is ours; an owner meeting it for the first time in a question cannot answer, and says so (reported 2026-08-26, against the wording these replaced: "the corpus wins about ___" asked them to complete a sentence that is not English unless you already know the ledger analogy).
Ask exactly this much. Do not explain what the answer will be used for inside the question — that is what made the last version unanswerable.
1 of 3 — What is this knowledge base about?
Be specific enough that I would know what does NOT belong in it.
Too vague: "our engineering docs" — I still could not tell what to leave out. Specific enough: "our leave, expense and conduct policies, current versions only."
2 of 3 — What is close to that, but not part of it?
Things people will ask this and it should NOT answer. A confident wrong answer is worse than "I do not cover that."
For the policies example: "not salaries, not individual HR cases, not last year's versions."
3 of 3 — Who signs off on a document, and who can take one down?
Names or handles, not job titles. If it is just you, say so.
Ask for BOTH: the handle the record will store (
human:bashiraziz) and the natural name to print ("Bashir Aziz"). They are not derivable from each other —human:cisoandhuman:mjsare not anybody's squashed full name — so the handle goes into the frontmatter and the policy, and the pair goes into.ksor/people.yamlfor the site to print.
Follow up until each is concrete, but follow up in their words too: "what would someone actually ask this?" gets further than "name the boundary".
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.
- 1mo ago Changed · +24 lines 164672012a90
- 1mo ago First seen · 154 lines · 84 tokens per session scan A 81555b3f2ea0
intake-interview is a skill published in the GitHub repository panaversity/ksor (232 stars, last pushed 23d ago), licensed Apache-2.0. It adds 84 tokens to every session and 2,355 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
csv-workbench
Analyze CSV files in /mnt/data and return concise numeric summaries.
surfsense-data
Work out numbers from spreadsheet and CSV sources (.xlsx, .csv, .tsv) by writing a pandas script that surfsenseanalyzedata runs: totals, averages, trends, rankings, comparisons, cleaning, and charts that can go into a document. Load it whenever the user asks for figures from a table, or a chart of one.
Create polished PDF files for requests such as PDFs, resumes, CVs, reports, letters, one-pagers, and printable documents.
review-artifact-comments
Only use when the user explicitly invokes this skill by name.
engineering-drawing
Make an engineering drawing of a part as a PDF - orthographic views with hidden lines and centre marks, real dimensions, hole callouts, notes and a title block on ISO sheets, all projected from the part's geometry so the drawing follows the model. Use when the user asks for a drawing, a dimensioned sheet, shop or…