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/fundamentalsnpx skills add DanielPodolsky/ownyourcode --skill fundamentalsgit 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/fundamentals)<a href="https://agentmods.dev/skills/danielpodolsky/ownyourcode/fundamentals"><img src="https://agentmods.dev/badge/skills/danielpodolsky/ownyourcode/fundamentals.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.00038 | $0.01445 |
| Opus 5 | $0.00019 | $0.00723 |
| Sonnet 5 | $0.00008 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
fundamentals-gate 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 3d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate 5: Fundamentals Review
"Good code is not just code that works. It's code that others can work with."
Purpose
This gate checks general code quality against engineering standards. Issues are SUGGESTIONS, not blockers — they're polish, not problems.
Gate Status
- PASS — Code quality is solid
- SUGGESTIONS — Minor improvements recommended
Gate Questions
Question 1: Naming Clarity
"Would a new developer understand what
[variable/function]does from its name alone?"
Looking for:
- Descriptive, intention-revealing names
- No abbreviations or single letters
- Boolean prefixes (is, has, can)
- Function verbs (get, set, handle)
Question 2: Function Focus
"Can you describe what this function does in one sentence without using 'and'?"
Looking for:
- Single responsibility
- Reasonable size (under 30 lines)
- Clear input/output relationship
- No hidden side effects
Question 3: Code Reuse
"I see this pattern in a few places. Is it intentional duplication or should it be extracted?"
Looking for:
- Awareness of duplication
- Appropriate abstraction (rule of three)
- Not over-engineering for one-time use
Fundamentals Checklist
Naming
- Variables are descriptive (no
temp,data,x) - Booleans prefixed with
is,has,can,should - Functions start with verbs
- No unnecessary abbreviations
- Consistent naming patterns
Functions
- Single responsibility
- Under 30 lines (generally)
- Fewer than 4 parameters
- Early returns instead of deep nesting
- No magic numbers (use named constants)
Structure
- Related code grouped together
- Appropriate file organization
- Clear separation of concerns
- Consistent formatting
Comments
- Explain WHY, not WHAT
- No commented-out code (delete it)
- No obvious comments (
// increment counter) - Complex logic documented
Response Templates
If PASS
✅ FUNDAMENTALS GATE: PASSED
Code quality is solid:
- Naming is clear and consistent
- Functions are focused
- Good structure overall
All gates passed! Let's move to code review...
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.
- 3d ago First seen · 242 lines · 38 tokens per session scan A ae7bf5417c5d
fundamentals-gate is a skill published in the GitHub repository DanielPodolsky/ownyourcode (276 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 1,445 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.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
agent-payments
Agent skill for payments - invoke with $agent-payments.
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-shared-state
Share structured, evolving state between an AG-UI agent and its client with the AG-UI .NET SDK — the client seeds state on the request, the server reads it, mutates it, and streams the updated state back as snapshots or deltas alongside the chat. USE FOR: sending initial/working state from the client via…