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 simota/agent-skills --skill siegegit clone --depth 1 https://github.com/simota/agent-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/simota/agent-skills/siege)<a href="https://agentmods.dev/skills/simota/agent-skills/siege"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/siege/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/simota/agent-skills/siege"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/siege.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Prompt Injection · line 6 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 96 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- low Excessive Agency · line 137 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00034 | $0.05539 |
| Opus 5.5 | $0.00014 | $0.02216 |
| Sonnet 5.5 | $0.00007 | $0.01108 |
| Haiku 4.5 | $0.00003 | $0.00554 |
Grade A, and why
siege 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 6d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
siege
Siege verifies system limits before users find them. It designs and audits load tests, contract tests, chaos experiments, mutation tests, and resilience checks. It reports evidence and recommended follow-up work; implementation fixes belong to partner agents.
What ships with it
16 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.
- _common 10 B
- reference/autorun-schema.md 784 B
- reference/chaos-engineering-guide.md 1.6 KB
- reference/chaos-observability.md 3.8 KB
- reference/contract-testing-patterns.md 4.5 KB
- reference/fuzz-testing-guide.md 9.3 KB
- reference/load-testing-anti-patterns.md 3.5 KB
- reference/load-testing-guide.md 4.5 KB
- reference/mutation-testing-advanced.md 3.9 KB
- reference/mutation-testing-guide.md 1.5 KB
- reference/property-based-testing.md 8.9 KB
- reference/resilience-anti-patterns.md 3.9 KB
- reference/resilience-patterns.md 3.8 KB
- reference/siege 11 B
- reference/smoke-deployment-gates.md 8.4 KB
- reference/test-strategy-2026.md 17 KB
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.
- 6d ago Changed · +1 lines 78ddcdbe526b
- 11d ago Changed 0922f908f139
- 13d ago Changed 91fc3df979bb
- 16d ago Changed 36695a6e78f9
- 1mo ago Changed · -1 lines 99cf45a29887
- 1mo ago First seen · 309 lines · 34 tokens per session scan A 8b86cfc21b49
siege is a skill published in the GitHub repository simota/agent-skills (95 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 5,539 once invoked, about $0.0001 per session on Opus 5.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
ai-prompt-regression-testing
Use when comparing prompt changes against a fixed evaluation set: record actual model settings, required checks, missing results, judge limitations and case-level regression evidence.
promptfoo-redteam-run
Execute, inspect, and rerun an existing Promptfoo redteam scan. Use for generated YAML, result exports, attack success rates, grader/target errors, filtered reruns, and CI gates. Use promptfoo-provider-setup for connections and promptfoo-redteam-setup for new scan plans.
promptfoo-redteam-setup
Create or refine a Promptfoo redteam config and generate probes from target behavior, code, or OpenAPI evidence. Use for purpose, trust boundaries, plugins, strategies, and grading guidance. Use promptfoo-provider-setup for connection work and promptfoo-redteam-run for an existing scan.
promptfoo-provider-setup
Connect Promptfoo to a model, live HTTP API, local Python/JavaScript provider, or app code. Use for request/auth mapping, response parsing, OpenAPI setup, and connection smoke tests. Use promptfoo-evals for broader eval coverage and promptfoo-redteam-setup for attack selection.
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Reviews code for bugs, security issues, and best practices.