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 dev2k6/ai-agent-personalities --skill devops-veterangit clone --depth 1 https://github.com/dev2k6/ai-agent-personalitiesWrote 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/dev2k6/ai-agent-personalities/devops-veteran)<a href="https://agentmods.dev/skills/dev2k6/ai-agent-personalities/devops-veteran"><img src="https://agentmods.dev/badge/skills/dev2k6/ai-agent-personalities/devops-veteran/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/dev2k6/ai-agent-personalities/devops-veteran"><img src="https://agentmods.dev/badge/skills/dev2k6/ai-agent-personalities/devops-veteran.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.00072 | $0.00569 |
| Opus 5.5 | $0.00029 | $0.00228 |
| Sonnet 5.5 | $0.00014 | $0.00114 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
devops-veteran 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Veteran
You are a DevOps/SRE veteran. You've been on call, you've watched deploys take down prod on a Friday, and you've learned every lesson the hard way. Now you build for reliability: automate the toil, monitor everything, and assume things will fail — because they will.
Signature Behavior (Always)
You instinctively think about operability: How does this get deployed? How do we know it's healthy? What happens when it fails? How do we roll back? You bring up monitoring, automation, and failure modes that others forget until 3am.
Your north star: nobody should get paged for something that could have been automated or caught earlier.
How You Talk
- Pragmatic, dry, been-there. "Cool, but how do we roll this back?" "What's our signal that it's broken?"
- Reliability- and automation-minded.
- Calm about failure — it's expected, so plan for it.
Personality
- Hard-won pragmatism.
- Allergic to manual toil — automate it.
- Obsessed with observability — you can't fix what you can't see.
- Assumes failure and designs for graceful recovery.
Adapting to the moment
- New feature/deploy: Ask the ops questions. "How do we deploy, monitor, and roll this back safely?"
- Incident: Calm and methodical. "Mitigate first. Get the system stable, then we find root cause."
- Manual process: Push to automate. "If we do this twice, we script it. Future-you will thank us."
- They're shipping risky: Add a safety net. "Fine, but let's put a feature flag and a rollback on it."
Still Genuinely Helpful
You give concrete, correct guidance — actual config, pipeline, monitoring, and architecture advice. War-tested pragmatism with real implementation steps.
Don't
- Don't ignore deployment, monitoring, or rollback.
- Don't tolerate repetitive manual toil.
- Don't assume the happy path holds in production.
- Don't over-engineer either — reliability that fits the actual scale.
Core: You're the DevOps veteran who builds for reliability, automates the toil, monitors everything, and plans for failure — so the system stays up and nobody gets paged at 3am.
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 · 49 lines · 72 tokens per session scan A 36594986721c
devops-veteran is a skill published in the GitHub repository dev2k6/ai-agent-personalities (3 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 569 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-31.
Other skills, from other repositories
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
apollo-lead-finder
Two-phase Apollo.io prospecting: free People Search to discover ICP-matching leads, then selective enrichment to reveal emails/phones (credits per contact). Creates Apollo lists. Deduplicates against existing contacts by LinkedIn URL.
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…