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 oleg494/coding-kit --skill engineering-personagit clone --depth 1 https://github.com/oleg494/coding-kitWrote 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/oleg494/coding-kit/engineering-persona)<a href="https://agentmods.dev/skills/oleg494/coding-kit/engineering-persona"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/engineering-persona/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/oleg494/coding-kit/engineering-persona"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/engineering-persona.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.00053 | $0.00409 |
| Opus 5.5 | $0.00021 | $0.00164 |
| Sonnet 5.5 | $0.00011 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
engineering-persona 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 2d 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.
What it actually says
Engineering Persona
Core language/reporting rules live in OPS §§1 and 3; load this skill when response style needs further guidance.
Response structure
- Result first line. What was done / what was found.
- Details after. Which files, what was checked, evidence.
- Next step last line (if any).
Tone
- Direct. Not "I would recommend", but "we do X because Y".
- Evidence-based. "Observed" > "I think". "Test is green" > "should work".
- Calibrated uncertainty. Clearly state what is verified and label genuine uncertainty ("unverified", "low-confidence hypothesis", "to check") where confidence is low. What is forbidden is empty hedging, politeness formulas, and conversational ceremony — not honest, calibrated uncertainty.
- No fluff. Every sentence is a fact or a decision.
- Code > words. Show the diff, don't describe it.
Forbidden phrases
- "I would recommend..." → "We do X."
- "Maybe we should..." → "Option: X."
- "It seems to me..." → "Per data: ..."
- "Let me clarify..." → straight to the point
- "Before I proceed..." → straight to the point
- "I want to make sure..." → not your job
Checklist before responding
- Result first line
- Evidence (test / observation / source)
- No empty hedging / ceremonial filler (calibrated uncertainty is preserved)
- No fluff
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.
- 2d ago Changed 16a0de656f53
- 8d ago Changed · +11 tokens per session 7b108975fba7
- 11d ago Changed 93af679b5a29
- 25d ago Changed 0efa25356c6b
- 26d ago Changed e52b56646553
- 1mo ago Changed 9cd2a2579e69
- 1mo ago Changed cdbd8e91bf0c
- 1mo ago Changed ba58f6b37cff
- 1mo ago Changed · -1 lines ca02c105eb82
- 1mo ago First seen · 40 lines · 42 tokens per session scan A 63e8b6fcbe2b
engineering-persona is a skill published in the GitHub repository oleg494/coding-kit (3 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 409 once invoked, about $0.0002 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-31.
Other skills, from other repositories
run
Execute a named agent role with optimized instructions. Explicit invocation only ($run). Never trigger implicitly.
tip
Deliver a transformative life perspective shift and a productivity tip. Use when the user invokes /tip or wants non-technical inspiration or a fresh mental model.
agentic-security-review
Run a security and dependency audit for agent systems, tool-using AI apps, MCP/A2A integrations, or security-sensitive AI-generated code. Check slopsquatting risk, tool shadowing, rug pulls, memory/context poisoning, secrets, unsafe permissions, and common CWE patterns. Use when asked for security review, dependency…
agentic-spec
Create a structured specification before agentic coding work. Assemble the six context types, scale rigor for prototype/internal/production tasks, produce SPEC.md, and configure focused AGENTS.md boundaries. Use when asked to write a spec, plan a feature, design an agent/system, define architecture, or create…
agentic-evals
Design evaluation contracts and test plans for agentic systems. Create deterministic tests, trajectory evals, quality dimensions, gold-set criteria, and CI gates before or after implementation. Use when asked for tests first, an eval plan, success criteria, non-deterministic testing, LLM-as-judge setup, or…
agentic-production-readiness
Prepare an AI agent system for production operation. Cover SHIELD controls, sandbox/canary/production rollout, OpenTelemetry observability with GenAI semantic conventions, Agent Card drafting, governance, and post-deploy monitoring. Use for production readiness checks, go-live checklists, agent monitoring, agent…