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/halidsaglam/saglitzsecure/remediationnpx skills add HalidSaglam/saglitzsecure --skill remediationgit clone --depth 1 https://github.com/HalidSaglam/saglitzsecureWrote 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/halidsaglam/saglitzsecure/remediation)<a href="https://agentmods.dev/skills/halidsaglam/saglitzsecure/remediation"><img src="https://agentmods.dev/badge/skills/halidsaglam/saglitzsecure/remediation.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.1 | $0.00044 | $0.02210 |
| Opus 5 | $0.00022 | $0.01105 |
| Sonnet 5 | $0.00009 | $0.00442 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade A, and why
remediation 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 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.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remediation
This skill is a three-stage loop: get the plan, apply it, prove it. No stage is skipped — least of all the last one. A fix is not finished when it has been written to a file; it is finished when a rescan has shown the finding closed.
If the question arrived before the code was written — "how do I build this safely?" — this skill is not the one in play; that question belongs to the secure-by-default skill, and auditing what has been written belongs to the security-audit skill. This skill closes findings that have already been found.
1. Get the baseline scan
If you do not have a usable scanId, call scan_project first. Verification is impossible
unless the state before the fix was recorded — to be able to say what closed, you need a "before"
to point back at.
remediation_plan and verify_fixes look at the same scanId. Do not use a scanId left
over from an older conversation or remembered by hand; use the id returned by the most recent
scan_project call. If the project changed after that scan (another fix, another commit), that
scanId is no longer a valid "before" — scan again.
2. Ask for a plan
Call remediation_plan with the fingerprint values of the findings to be fixed (findingIds)
and the scanId from step 1. Those fingerprints must come from the same scan: given a
fingerprint that is not in the scan, remediation_plan does not return a partial plan, it
throws. Never pass a fingerprint copied from an older scan or typed out by hand; always use the
fingerprint fields from the scan_project output you just took. If you get an error, refresh
the scan and take the fingerprints from it again — a plan is not left half-done and carried on
with.
The returned steps list is sorted by the order field, and that order is kept. The order
is not arbitrary: revoking the key inside .env without having added .env to .gitignore
lets the key leak again in the next commit. Do not reorder the steps by severity, by file name
or by your own preference.
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 · 143 lines · 44 tokens per session scan A 5922c923ed29
remediation is a skill published in the GitHub repository HalidSaglam/saglitzsecure (0 stars, last pushed 8d ago), licensed MIT. It adds 44 tokens to every session and 2,210 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…