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/vulnerscom/api/vulners-apinpx skills add vulnersCom/api --skill vulners-apigit clone --depth 1 https://github.com/vulnersCom/apiWhat 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.00079 | $0.02241 |
| Opus 5 | $0.00039 | $0.01120 |
| Sonnet 5 | $0.00016 | $0.00448 |
| Haiku 4.5 | $0.00008 | $0.00224 |
Grade A, and why
vulners-api-python-sdk 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulners API Python SDK skill
Purpose
Maintain the Vulners Python API SDK safely and consistently.
Use this skill for:
- Editing the
src/vulners/package (v4 core or the legacy v3 layer). - Adding SDK methods for Vulners API endpoints.
- Writing or updating tests under
tests/. - Updating examples in
samples/and documentation underdocumentation/. - Reviewing README changes, release automation, and API-key handling.
Do not use this skill for:
- Storing or generating real Vulners API keys.
- Writing exploit weaponization/execution code or operational abuse workflows.
- Moving non-runtime agent instructions into the
src/vulners/package.
Repository context
This skill is consumed from .agents/skills/vulners-api/SKILL.md by Codex-compatible
agent harnesses. This repository is the source of truth for the skill.
Current repository layout (src layout, uv_build backend):
api/
├── .agents/skills/vulners-api/ # this skill
├── dev-tools/ # maintainer tooling (not shipped)
├── documentation/ # mkdocs site source (Material theme)
├── samples/ # runnable examples: v4/ and legacy/
├── src/vulners/ # the shipped package
├── tests/ # pytest suite (core, bc, live, benchmarks)
├── Makefile
├── mkdocs.yml
└── pyproject.toml
Architecture
The primary API is the pair of typed clients in src/vulners/_client.py:
Vulners(sync) andAsyncVulners(async), re-exported from the package root.- Resources hang off each client as
cached_propertynamespaces:search,audit,archive,misc,report,stix,subscriptions,subscriptions_v4,webhooks,vscanner(which nestslicenses,projects,projects.tasks,projects.results). - Each resource method declares its endpoint as a module-level
RequestSpec(method, path, body mode, unwrap keys, timeout profile, rate-limit group) and routes through one shared request pipeline: credential-safety transport, retries withRetry-Aftersupport, and token-bucket rate-limit pacing. client.get/post/put/deleteare untyped escape hatches for any API path.
What ships with it
5 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 · 194 lines · 79 tokens per session scan A ce5d6f7b3cc5
vulners-api-python-sdk is a skill published in the GitHub repository vulnersCom/api (371 stars, last pushed 11d ago), licensed MIT. It adds 79 tokens to every session and 2,241 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-30.
Other skills, from other repositories
release
Create a new SDK release — bump version, update HISTORY.md, and commit on a release branch.
python-asyncio-concurrency
Write correct asyncio Python — event loop, tasks, locking, timeouts, and avoiding blocked/leaked coroutines.
generate-v9-models
Generate pyatlanv9 msgspec model files by cloning the models repo and running the Pkl code generator.
upgrade-deps
Upgrade all pyatlan Python dependencies and GitHub Actions to their latest compatible versions.
python-async-patterns
5 async patterns with full implementations for Python concurrent programming.
security-vulnerability-scanner
Enterprise security vulnerability scanner that detects OWASP Top 10 vulnerabilities, provides CVSS-based risk scoring, generates remediation guidance, checks for known CVEs, and produces SBOM reports.