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/danielpodolsky/ownyourcode/star-storiesnpx skills add DanielPodolsky/ownyourcode --skill star-storiesgit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWrote 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/danielpodolsky/ownyourcode/star-stories)<a href="https://agentmods.dev/skills/danielpodolsky/ownyourcode/star-stories"><img src="https://agentmods.dev/badge/skills/danielpodolsky/ownyourcode/star-stories.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.00035 | $0.01296 |
| Opus 5 | $0.00017 | $0.00648 |
| Sonnet 5 | $0.00007 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
star-story-extraction 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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STAR Story Extraction
"Every feature you build is an interview answer waiting to be told."
Purpose
Transform completed work into compelling interview stories using the STAR method. These stories demonstrate real problem-solving ability.
The STAR Method
| Component | Question | Focus |
|---|---|---|
| Situation | "What was the context?" | Set the scene, explain the problem |
| Task | "What were YOU responsible for?" | YOUR specific role and responsibility |
| Action | "What did YOU do?" | Specific technical actions YOU took |
| Result | "What was the outcome?" | Impact, metrics, improvements |
Extraction Flow
Step 1: Identify the Story Type
What kind of problem did you solve?
| Story Type | Good For Questions Like |
|---|---|
| Technical challenge | "Tell me about a difficult bug you solved" |
| Feature implementation | "Describe a feature you're proud of" |
| Performance optimization | "How did you improve system performance?" |
| Security fix | "Tell me about a security issue you addressed" |
| Refactoring | "Describe a time you improved code quality" |
| Learning curve | "Tell me about a time you learned something quickly" |
Step 2: Guide Through STAR
Situation (2-3 sentences)
"What was the context? What problem or challenge existed before you started?"
Good elements:
- Business context (why it mattered)
- Technical constraints
- Scale/impact of the problem
Avoid:
- Too much background
- Irrelevant details
- Blaming others
Task (1-2 sentences)
"What were YOU specifically responsible for? What was your role?"
Good elements:
- Clear ownership
- Specific scope
- Why you were the one to do it
Avoid:
- "We did this" (use "I")
- Vague responsibilities
Action (The meat - 3-5 sentences)
"Walk me through the specific steps YOU took. Be technical."
Good elements:
- Specific technologies used
- Problem-solving approach
- Trade-offs considered
- Technical decisions made
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.
- 5d ago First seen · 196 lines · 35 tokens per session scan A ce6497656a18
star-story-extraction is a skill published in the GitHub repository DanielPodolsky/ownyourcode (281 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,296 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-08-30.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
nw-ddd-eventsourcing
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution.