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 kirilxd/swe-interview-coach --skill behavioral-frameworksgit clone --depth 1 https://github.com/kirilxd/swe-interview-coachWrote 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/kirilxd/swe-interview-coach/behavioral-frameworks)<a href="https://agentmods.dev/skills/kirilxd/swe-interview-coach/behavioral-frameworks"><img src="https://agentmods.dev/badge/skills/kirilxd/swe-interview-coach/behavioral-frameworks/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/kirilxd/swe-interview-coach/behavioral-frameworks"><img src="https://agentmods.dev/badge/skills/kirilxd/swe-interview-coach/behavioral-frameworks.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.00067 | $0.02004 |
| Opus 5.5 | $0.00027 | $0.00802 |
| Sonnet 5.5 | $0.00013 | $0.00401 |
| Haiku 4.5 | $0.00007 | $0.00200 |
Grade A, and why
behavioral-frameworks 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavioral Frameworks
STAR (Situation, Task, Action, Result)
Primary structure for behavioral answers. Every story should map to exactly one S, T, A, R.
Situation
The context that made the problem worth solving. Sets stakes without over-explaining.
- Name the product/system/team and its scale (users, dollar impact, team size).
- Surface the constraint or threat that created urgency — why did this matter now.
- Keep it to 2-3 sentences; interviewers need orientation, not a history lesson.
Weak: "We had a frontend codebase that was getting kind of hard to work with and everyone was writing their own components."
Strong: "At Acme, our five frontend teams were duplicating UI components across three apps. QA bounce-backs on UI-heavy features ran at ~40%, and each sprint lost roughly two engineer-days to inconsistent implementations."
Task
The specific outcome you were accountable for — your mandate, not the team's.
- State your ownership explicitly: "I was responsible for…" not "the team needed to…"
- Distinguish your goal from the broader business goal (they can differ).
- Name any constraints: timeline, budget, staffing, political opposition.
Weak: "We decided to build a shared component library so things would be more consistent."
Strong: "I was tasked with designing and driving adoption of a shared component library with a hard deadline of Q2 — without a formal mandate, meaning I needed buy-in from five team leads who had no obligation to participate."
Action
The decisions you made and the steps you took. This is the longest element (~50% of the answer).
- Use "I" — own the decisions. Reserve "we" for work the team genuinely did autonomously.
- Sequence decisions, not just activities: what did you decide, and why did you choose that path over alternatives?
- Include at least one obstacle and how you navigated it.
Weak: "We built the library, documented it, and did roadshows to get people to use it. We also added linting rules and set up CI checks."
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 First seen · 144 lines · 67 tokens per session scan A 6b76e602503a
behavioral-frameworks is a skill published in the GitHub repository kirilxd/swe-interview-coach (91 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 2,004 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
bq-skill
A coaching workflow for building a reusable library of truthful stories for behavioral job interviews. It uses structures such as STAR—Situation, Task, Action, Result—and can connect stories to a job description and résumé.
learning-and-development
Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
onboarding-express
AI-guided architectural tour of any codebase — entry points, business logic, and the most complex module in one structured pass, powered by Graph-It-Live. Use this skill whenever someone is new to a codebase or wants a quick orientation. Trigger for: "I just joined this team", "explain this repo to me", "give me a…
teach-me
Teach the learner to deeply understand a body of work — the current session's changes, a PR, an ADR, or any topic they name — the problem and why it existed, the solution and why it was built that way, and why it matters, incrementally and confirming mastery at each stage before advancing. Use when the user wants to…
creating-explainers
Use when creating an interactive explainer - a single self-contained HTML page with hand-built Canvas figures. Handles source-file explainers, topic-driven research explainers, and mixed intake where files provide the spine and research adds support. Trigger phrases include "make an explainer", "turn this paper into…