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 OutlineDriven/outline-driven-development --skill culture-interview-profile-predictiongit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/culture-interview-profile-prediction)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/culture-interview-profile-prediction"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/culture-interview-profile-prediction/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/outlinedriven/outline-driven-development/culture-interview-profile-prediction"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/culture-interview-profile-prediction.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.00038 | $0.01360 |
| Opus 5 | $0.00019 | $0.00680 |
| Sonnet 5 | $0.00008 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
culture-interview-profile-prediction 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Culture interview profile prediction
Contract
| Field | Bound contract |
|---|---|
| Trigger | An interview transcript needs a caveated, confidence-scored prediction of Culture Index traits before a survey exists. |
| Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. Analyzes supplied transcript text only. |
| Side effect | Chat output: per-trait predictions, confidence levels, supporting quotations, likely pattern, uncertainty areas, and caveats. |
| Done | All six traits have evidence and confidence, weak evidence is labeled, and the output clearly distinguishes prediction from survey result. |
Inputs
- Required: An interview transcript with interviewer questions and candidate responses distinguishable. Multiple interviews increase confidence.
- Optional: Timestamps or durations. Candidate name and interview metadata for the report header.
Procedure
-
Load the transcript. Confirm interviewer questions and candidate responses are distinguishable. If they are not, stop and request a separated transcript. Done when: this step's stated action, evidence, and checks are complete.
-
Initial read-through. Note overall communication style, energy level, topics that engage the candidate, and default communication mode before detailed analysis. Done when: this step's stated action, evidence, and checks are complete.
-
Analyze A (Autonomy). Search the transcript for autonomy signals. High A: first-person ownership ("I decided", "I built"), takes personal credit, reframes or pushes back on questions, acted without being asked, assertive tone. Low A: collective language ("we decided", "our team"), deflects credit to team, asks for clarification, waited for direction, tentative tone. Record position (High / Low / Normative), confidence (High / Medium / Low), and 2-3 supporting quotes. Done when: this step's stated action, evidence, and checks are complete.
-
Analyze B (Social). Search for social signals. High B: builds rapport, asks about the interviewer, people-centric narratives, verbose responses, animated energy, asks about team and social activities. Low B: gets straight to business, task-centric descriptions, brief direct answers, reserved energy, asks about work and tools. Record position, confidence, and 2-3 quotes. Done when: this step's stated action, evidence, and checks are complete.
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 Changed · -5 tokens per session b4d02ab3c355
- 7d ago First seen · 54 lines · 43 tokens per session scan A 39685edd9e7e
culture-interview-profile-prediction is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 5d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,360 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
goal-prompt-drafting
Use when asked to draft copy-ready /goal objectives for long-running agents; returns one normalized one-line objective with measurable end state, grounded proof, easy-out invariants, a stop clause, and a Missing list. Not for source or remote-system changes.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.