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 initlabsai/vibekit --skill audit-algorandgit clone --depth 1 https://github.com/initlabsai/vibekitWrote 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/initlabsai/vibekit/audit-algorand)<a href="https://agentmods.dev/skills/initlabsai/vibekit/audit-algorand"><img src="https://agentmods.dev/badge/skills/initlabsai/vibekit/audit-algorand/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/initlabsai/vibekit/audit-algorand"><img src="https://agentmods.dev/badge/skills/initlabsai/vibekit/audit-algorand.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 Memory Poisoning · line 48 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Prompt Injection · line 44 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00097 | $0.01264 |
| Opus 5 | $0.00048 | $0.00632 |
| Sonnet 5 | $0.00019 | $0.00253 |
| Haiku 4.5 | $0.00010 | $0.00126 |
Grade A, and why
audit-algorand 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 9d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Algorand contracts
Audit the behavior an attacker can reach, then explain each issue through a violated invariant and a reproducible path. A checklist is coverage support; it is not evidence that a vulnerability exists.
This skill covers Algorand TypeScript and PuyaTs. Do not introduce Python,
PyTEAL, Beaker, or raw-TEAL implementation guidance. Load build-on-algorand
when the user also asks to implement fixes or needs broader PuyaTs application
guidance. Load use-vibekit before any deployment, signing, network, account,
LocalNet, or on-chain action.
Establish scope before judging safety
Read the repository instructions, package manifests, lockfile, compiler configuration, contract source, generated ARC-56 and TEAL artifacts, clients, and tests that are in scope. Use the project's pinned commands and dependencies. Do not add a dependency or change production code during an audit unless the user explicitly asks for remediation.
Record:
- the reviewed commit or working-tree state;
- included contracts, LogicSigs, clients, artifacts, and tests;
- target network and active or assumed consensus protocol;
- compiler and optimization settings;
- excluded components and assumptions;
- whether generated artifacts match the reviewed source;
- commands that ran, failed, or could not run.
Treat missing source, stale artifacts, failing tests, and unverified deployment bytecode as limitations. Do not silently fill those gaps with assumptions.
Load the audit guides
Read Methodology and reporting for every audit. Then load every guide whose feature appears in the system:
| Surface | Guide |
|---|---|
| ABI methods, privileges, lifecycle handlers, upgrades, deletion, pausing | Applications and authorization |
| Payments, asset transfers, inner transactions, fees, atomic groups, ASA control | Transactions and assets |
| Local/global/box state, clear state, MBR, state machines, accounting, numeric formulas | State and arithmetic |
| Contract-account or delegated smart signatures | Logic Signatures |
| Randomness, oracles, compiler and artifact verification, clients, keys, monitoring | External systems and release |
What ships with it
6 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.
- 9d ago First seen · 129 lines · 97 tokens per session scan A c207c0704d8a
audit-algorand is a skill published in the GitHub repository initlabsai/vibekit (27 stars, last pushed 6d ago), licensed MIT. It adds 97 tokens to every session and 1,264 once invoked, about $0.0005 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
algorand-interaction
Interact with Algorand blockchain via the Algorand MCP server — wallet operations, ALGO/ASA transactions, smart contracts, account info, NFD lookups, atomic groups, Tinyman swaps, Haystack Router best-price swaps, Alpha Arcade prediction markets, Pera asset verification, TEAL compilation, knowledge base. Use when user…
alpha-arcade-interaction
Trade on Alpha Arcade prediction markets on Algorand — browse markets, read orderbooks, place limit/market orders, manage positions, cancel/amend orders, split/merge shares, and claim winnings. Use when user asks about prediction markets, event betting, YES/NO shares, orderbooks, or Alpha Arcade.
haystack-router-interaction
Route and execute optimal token swaps on Algorand using Haystack Router via Algorand MCP tools. Use when getting best-price quotes across multiple Algorand DEXes and LST protocols, executing atomic swaps, and checking asset opt-in — all through the Algorand MCP server.
algorand-x402-payment
Execute x402 payments at runtime using Algorand MCP tools. Use whenever an HTTP request returns 402 Payment Required (or a PAYMENT-REQUIRED header), the user needs to access a paid API or x402-protected resource, or the user mentions x402, micropayments, paying for an endpoint, or "payment required" — even if they…
use-wallet
Integrate Algorand/AVM wallet connections using @txnlab/use-wallet v4.x. Use when building dApps that need wallet connectivity (Pera, Defly, Lute, Kibisis, Exodus, WalletConnect, etc.), transaction signing, data signing (ARC-60/SIWA), network switching, or wallet state management in vanilla JS/TS, React, Vue, SolidJS…
nfd
Work with NFDomains (NFDs), the Algorand Name Service (.algo domains), using the @txnlab/nfd-sdk TypeScript SDK. Use when building features that involve resolving .algo domain names to addresses (or reverse), displaying NFD avatars and metadata, searching for NFDs, minting new NFDs, purchasing NFDs from the…