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/emre-guler/websec/secretsnpx skills add emre-guler/websec --skill secretsgit clone --depth 1 https://github.com/emre-guler/websecWhat 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.00084 | $0.05528 |
| Opus 5 | $0.00042 | $0.02764 |
| Sonnet 5 | $0.00017 | $0.01106 |
| Haiku 4.5 | $0.00008 | $0.00553 |
Grade A, and why
secrets 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 2d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Committed Secret Detection
Overview
A secret is credential material whose value alone grants access: an API key, a bearer token, a password, a connection string, a private key, a signing key, a cloud access pair. This class is about such material being in the artefact — committed to the repository, packaged into an image, inlined into a bundle the browser downloads, or left in a revision nobody looks at any more. The attacker needs no request and no flaw: a fork, a leaked archive, a published package, a departed contributor's clone, a build log, or a browser's network tab is enough. What they gain is whatever the value unlocks, from another party's paid quota to the production database, obtained directly, bypassing every control the application implements. The judgement that decides a finding is never entropy: it is whether the value is live and what it opens. This skill finds such material by locating every credential-shaped value in the tree, its history, and everything shipped to a client, verifying each one in parallel, and merging the results into <output_dir>/secrets-results.md.
What it is NOT
- A value the running application serves (
/websec:information-disclosure): a credential in a stack trace, a diagnostic endpoint that dumps the environment, a configuration file reachable under a served root. Test: does the value reach the attacker because a running process emitted it, or because it is baked into a file the repository or the build produced? Runtime emission is theirs; committed or built-in material is here. - How a key is used (
/websec:crypto): a key derived from a passphrase, one key serving every purpose, a nonce reused, a comparison that leaks timing. Test: replace the value with a strong one from a managed source — if the finding survives, it is theirs; if the whole finding is that this value is in the repository, it is here. - What a weak signing secret lets an attacker do (
/websec:jwt): forging tokens, algorithm handling, claim assertion. Test: the fact that the signing secret is committed or is a short literal is here; the impersonation it enables, and everything about how the token is accepted, is theirs. - An endpoint that hands a credential back (
/websec:api): a route returning a key in its body, a serialiser that includes a token field. Test: is the credential in a file, or in a response a route produces? The second is theirs. - Not a finding: an unmistakable placeholder in an example file; an identifier a provider documents as publishable and safe for a client; a public key or certificate, as distinct from the private half; a fixture credential for a service that exists only on a developer machine and nowhere else. Presence of a high-entropy string is never the finding on its own — liveness and what it unlocks must both be argued.
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.
- 2d ago First seen · 161 lines · 84 tokens per session scan A 5e1df09fc249
secrets is a skill published in the GitHub repository emre-guler/websec (2 stars, last pushed 5d ago), licensed MIT. It adds 84 tokens to every session and 5,528 once invoked, about $0.0004 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
vantage
Autonomous, artifact-driven SAST (Static Application Security Testing) for web AND mobile app repositories, plus optional code-level remediation. Use whenever the user asks to security-review, pentest, audit, or scan a codebase for vulnerabilities — web (SQLi, XSS, IDOR/BOLA, auth bypass, SSRF, XXE, hardcoded secrets…
prowler-ui
Prowler UI-specific patterns. For generic patterns, see: typescript, react-19, nextjs-16, tailwind-4. Trigger: When working inside ui/ on Prowler-specific conventions (shadcn, folder placement, actions/adapters, shared types/hooks/lib).
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
prowler-pr
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml…
tailwind-4
Tailwind CSS 4 patterns and best practices. Trigger: When styling with Tailwind (className, variants, cn()), especially when dynamic styling or CSS variables are involved (no var() in className).
prowler-docs
Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.