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/gaelic-ghost/socket/preserve-security-evidencenpx skills add gaelic-ghost/socket --skill preserve-security-evidencegit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/preserve-security-evidence)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/preserve-security-evidence"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/preserve-security-evidence.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.00049 | $0.00474 |
| Opus 5 | $0.00024 | $0.00237 |
| Sonnet 5 | $0.00010 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
preserve-security-evidence 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 yesterday.
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preserve Security Evidence
Overview
Create a reproducible security record while keeping originals and observations distinct from transformed working material. Prioritize volatile evidence when delay would erase it, but state when urgent harm reduction must take precedence.
Read references/security-record.md for the shared record and transformation shapes.
Workflow
-
Define the question and evidence owner.
- Record the affected person/system, requested decision, acquisition source, time, and analyst.
- Record authorization and disclosure limits when they matter.
-
Separate original and working material.
- Avoid opening active content during preservation.
- Copy artifacts into a clearly named working area when analysis requires mutation.
- Record every extraction, decoding, re-sign, patch, conversion, or replay as a transformation that creates a new artifact identity.
-
Capture stable identity.
- Record paths or logical identifiers, sizes, timestamps, cryptographic hashes, versions, bundle/package identifiers, UUIDs, signer identity, and source URLs when applicable.
- Record tool name, version, command, configuration, and environment for consequential observations.
-
Prioritize volatile state.
- Capture time, logged-in users, processes and ancestry, open files, network state, relevant memory or runtime telemetry, and transient logs only when authorized and proportionate.
- Do not collect unrelated personal or secret data merely because access is available.
-
Maintain evidence quality.
- Store observations, external intelligence, hypotheses, conclusions, and disproven hypotheses separately.
- Preserve raw output alongside summaries when safe.
- Mark missing data, collection failures, time skew, incomplete coverage, and evidence destroyed by containment.
-
Produce a handoff.
- State which inputs are originals, which are working copies, what changed, and which next workflow should consume them.
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.
- yesterday First seen · 46 lines · 49 tokens per session scan A 58367e09bc21
preserve-security-evidence is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 49 tokens to every session and 474 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-09-03.
Other skills, from other repositories
pipeline
Use when the user wants a feature idea taken end-to-end in one autonomous run — phrases like "run the whole pipeline", "take this feature from idea to finished branch", "brainstorm then build it autonomously", "do everything from idea to merged", "implement all phases without stopping". Triggers when they want…
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
voice-of-customer
Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act…
business-growth-consultant
Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when…