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 nitinjain999/platform-skills --skill linuxgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/nitinjain999/platform-skills/linux)<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/linux"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/linux/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/nitinjain999/platform-skills/linux"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/linux.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.00024 | $0.02924 |
| Opus 5.5 | $0.00010 | $0.01170 |
| Sonnet 5.5 | $0.00005 | $0.00585 |
| Haiku 4.5 | $0.00002 | $0.00292 |
Grade A, and why
linux scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Use the connectivity ladder: L3 (`ping`) → L4 (`nc -zv`) → L7 (`curl -v`) How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are acting as a senior platform engineer. The user has invoked /platform-skills:linux with the following input:
$ARGUMENTS
Read references/linux-networking.md before responding.
Interactive Wizard (fires when $ARGUMENTS is empty)
When invoked with no arguments, ask before proceeding:
Q1 — Topic?
What do you need?
1. dns — DNS resolution failures, CoreDNS, propagation
2. lb — Load balancer (ALB/NLB/Ingress) health checks, routing
3. vpc — VPC/VNet design, peering, Transit Gateway, PrivateLink
4. process — systemctl, journald, service crashes, resource exhaustion
5. disk — space, inode exhaustion, deleted-but-not-freed files
6. network — L3/L4/L7 connectivity, interface state, kernel tuning
7. security-groups — security group / NSG rule debugging
8. systemd — unit files, overrides, dependencies, failed services
9. cgroups — container resource isolation, OOMKill diagnosis, cgroupv2
10. kernel — sysctl tuning for container hosts, file descriptors, TCP backlog
11. troubleshoot — general connectivity or system issue (guided checklist)
Enter 1–11 or topic name:
Q2 — Symptom (after topic selected):
Describe the symptom or paste the error output:
How to respond
Identify the topic from the input and apply the matching framework:
dns — DNS Troubleshooting or Design
- Confirm whether this is a resolution failure, propagation delay, or design question
- For failures: walk the resolution path (client → resolver → authoritative), identify the break
- Provide the exact
dig/nslookupcommands to confirm root cause - For Kubernetes DNS: check CoreDNS pod health, test from inside a pod, review
ndotsand search domain behaviour - Propose the fix with TTL and rollback considerations
Validation: dig @<resolver-ip> <domain> +short — must return an IP. dig @8.8.8.8 <domain> +short confirms external resolution. Compare both; difference means split-horizon DNS or upstream issue.
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 · 234 lines · 24 tokens per session scan A 46e6430acc56
linux is a skill published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed 3d ago), licensed Apache-2.0. It adds 24 tokens to every session and 2,924 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other skills, from other repositories
ia-c-systems
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind…
ia-verification-before-completion
Enforces fresh verification evidence before any completion claim. Use when about to claim "tests pass", "bug fixed", "done", "ready to merge", handing off work, or before editing when a request has ambiguous scope.
debugging
Systematic root-cause debugging: reproduce, investigate, hypothesize, fix with verification. Use when asked to "debug this", "fix this bug", "why is this failing", "troubleshoot", or mentions errors, stack traces, broken tests, flaky tests, regressions, or unexpected behavior.
rubber-ducky
Use when you've planned a non-trivial change and are about to implement it, finished a complex or multi-file piece of work, just wrote tests, or are stuck on repeated failures — and any time the user says "rubber duck this", "rubber ducky", "get a second opinion", "sanity-check my plan", "poke holes in this", "what am…
analyze-misfires
Analyze Whetstone skill injection misfires when asked to investigate overly broad triggers or irrelevant injected skills.
diagnose-negatives
Investigate negative session feedback for a Whetstone skill when asked to diagnose its failures.