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 OutlineDriven/outline-driven-development --skill core-dumpsgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/core-dumps)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/core-dumps"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/core-dumps/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/outlinedriven/outline-driven-development/core-dumps"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/core-dumps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 44 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00047 | $0.01696 |
| Opus 5 | $0.00023 | $0.00848 |
| Sonnet 5 | $0.00009 | $0.00339 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade B, and why
core-dumps scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo sysctl -w kernel.core_pattern=/tmp/core-%e-%p-%t How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core dumps
Contract
| Field | Bound contract |
|---|---|
| Trigger | A program crashed and left a core file, cores need enabling on Linux or macOS, symbols are missing for a production binary, or a backtrace is needed without re-running the program. |
| Authority | Read-only. Emits analysis and commands for the operator to run on the target; no file writes, no rollback needed. No remote mutation. |
| Side effect | Diagnostic commands and a crash verdict in chat. Nothing is written. |
| Done | The crashing frame, signal, and faulting access are named, or the missing prerequisite (symbols, core file, build ID) is stated. |
Inputs
- Core file or crash record (required): a
corefile, acoredumpctlentry, or a/cores/core.<PID>file on macOS. - Binary (required): the exact executable that crashed, ideally the unstripped build.
- Build ID or debug package access (optional): needed when the binary is stripped.
Procedure
-
Enable cores on Linux.
ulimit -c unlimited # this shell only ulimit -c # confirm cat /proc/self/limits # per-process viewPersist for all users in
/etc/security/limits.conf:* soft core unlimited * hard core unlimitedControl where cores land:
cat /proc/sys/kernel/core_pattern sudo sysctl -w kernel.core_pattern=/tmp/core-%e-%p-%t%eis the executable name,%pthe PID,%tthe timestamp. If the pattern starts with|, a pipe handler such as systemd-coredump or apport owns core collection; use step 2 instead of looking for files. Done when:ulimit -creports unlimited and the pattern names a writable path or a known pipe handler. -
Use coredumpctl when systemd collects cores.
coredumpctl list # recorded crashes coredumpctl list myapp # crashes of one executable coredumpctl info # details of the latest coredumpctl gdb # open the latest in GDB coredumpctl gdb 12345 # open a specific PID coredumpctl dump 12345 -o myapp.core # export the core file
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 158 lines · 47 tokens per session scan B 5d622c3de3f1
core-dumps is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 4d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,696 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other skills, from other repositories
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
debug
Hypothesis-driven debugging. Use when a test fails, a crash or exception occurs, output is wrong, or an intermittent flake has no obvious cause.
optimize
Use when asked to optimize code, speed up a path, reduce allocations, repair a regression, or profile a target. Not for remote, credential, publish, deploy, or irreversible changes.
ios-build-fix
Use when asked to run /ios-build-fix to fix a failing iOS build, regenerate an Xcode project from project.yml, or correct UI behavior. Not for a clean rebuild: use ios-build-cleanup.
strike-the-root
Use when a bug, failure, flake, regression, review finding, or ticket needs the core fixed so it cannot recur. Not for greenfield features: use tdd. Not for style-only review or typo-class one-liners.
extremely-optimize
Use when asked to run a performance campaign against a measured floor. Not for hypothesis-only analysis without mutation: use fastopt.