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 Goldziher/spikard --skill common-task-commandsgit clone --depth 1 https://github.com/Goldziher/spikardWrote 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/goldziher/spikard/common-task-commands)<a href="https://agentmods.dev/skills/goldziher/spikard/common-task-commands"><img src="https://agentmods.dev/badge/skills/goldziher/spikard/common-task-commands.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00003 | $0.00738 |
| Opus 5 | $0.00002 | $0.00369 |
| Sonnet 5 | $0.00001 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
common-task-commands 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 8d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
priority: critical
Common Task Commands
Setup & Installation:
task setup: Install all dependencies (Rust, Python, Node, Go, Java, Ruby, etc.)poly hooks install: Install poly's git hook shims
Build Commands:
task build: Build core only (respects BUILD_PROFILE)task build:bindings: Build language bindings explicitlytask build:all: Build core plus bindings explicitlytask rust:build: Build Rust core (respects BUILD_PROFILE)task rust:build:dev: Build Rust in debug modetask rust:build:release: Build Rust in release modetask python:build: Build Python bindings (maturin)task node:build: Build TypeScript/Node bindings (NAPI-RS)task go:build: Build Go bindingstask java:build: Build Java bindings (Maven)task ruby:build: Compile Ruby native extensionstask csharp:build: Build C# bindingstask wasm:build: Build WebAssembly bindings
Test Commands:
task test: Run core tests (respects BUILD_PROFILE)task rust:test: Run Rust teststask python:test: Run Python tests (pytest)task node:test: Run TypeScript tests (vitest)task go:test: Run Go teststask java:test: Run Java tests (Maven)task ruby:test: Run Ruby tests (RSpec)task e2e:generate: Generate E2E tests from fixturestask e2e:build: Build bindings and generated E2E support binariestask e2e:test: Run E2E teststask e2e:all: Run all E2E tests across all languages
Linting & Formatting:
task lint: Lint current projecttask lint:all: Lint all languagestask lint:check: CI linting (for GitHub Actions, fails on issues)task format: Format repo code (auto-fixes); excludes Alef formattingtask format:check: Check formatting (fails if needs formatting)task alef:format: Format Alef-generated output explicitlytask rust:fmt: Format Rust (cargo fmt)task rust:clippy: Lint Rust (cargo clippy)task python:lint: Lint Python (ruff, mypy)task python:format: Format Python (ruff, black)task node:lint: Lint TypeScript (biome)task node:format: Format TypeScript (biome)
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.
- 8d ago First seen · 74 lines · 3 tokens per session scan A 764a6b6197b1
common-task-commands is a skill published in the GitHub repository Goldziher/spikard (119 stars, last pushed 25d ago), licensed MIT. It adds 3 tokens to every session and 738 once invoked, about $0.0000 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
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
notion-to-blog
Transfer a blog post from Notion to the Wasp blog. Fetches content, downloads and optimizes images, and creates a properly formatted MDX file.
geo-fundamentals
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
i18n-parity
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change…