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/proluct/skanna/hello-skillnpx skills add proluct/skanna --skill hello-skillgit clone --depth 1 https://github.com/proluct/skannaWrote 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/proluct/skanna/hello-skill)<a href="https://agentmods.dev/skills/proluct/skanna/hello-skill"><img src="https://agentmods.dev/badge/skills/proluct/skanna/hello-skill.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.00036 | $0.00139 |
| Opus 5 | $0.00018 | $0.00069 |
| Sonnet 5 | $0.00007 | $0.00028 |
| Haiku 4.5 | $0.00004 | $0.00014 |
Grade A, and why
hello-skill 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 4d 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.
What it actually says
hello-skill
When the user asks for a greeting, produce one:
- Take the name the user provided; if none was given, ask for one.
- Reply with
Hello, <name>! Welcome aboard.in the conversation. - Do not write any files; the greeting is chat output only.
That is the whole job. This fixture exists so scanners have a known-clean package to verify against.
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.
- 4d ago First seen · 16 lines · 36 tokens per session scan A 4523a8193df9
hello-skill is a skill published in the GitHub repository proluct/skanna (6 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 139 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
performing-supply-chain-attack-simulation
Simulate and detect software supply chain attacks including typosquatting detection via Levenshtein distance, dependency confusion testing against private registries, package hash verification with pip, and known vulnerability scanning with pip-audit.
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
sbom-analysis
Analyzes Software Bills of Materials (SBOMs) for completeness against NTIA minimum elements, interprets VEX status documents, performs transitive dependency risk analysis, and detects license conflicts. Supports CycloneDX 1.5 and SPDX 2.3 formats with CSAF-based VEX correlation. Auto-invoked when SBOM files are…
supply-chain-security
Vet dependencies before they enter the build: typosquats, dependency confusion, malicious packages, known vulnerabilities, unlocked resolution, risky install and build hooks, EOL embedded runtimes, and the authenticity and freshness of your own release channel. Use when adding or upgrading a dependency, reviewing…
testing-trustcard-behavior
End-to-end verification of the trustcard behavioral verification engine (lib/behavior.js and the mcp-trustcard behavior CLI).
testing-trustcard-rfc
Verify RFC documentation and HTML mockup assets for the trustcard npm install trust check RFC.