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/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/goldziher/spikard/common-task-commands"><img src="https://agentmods.dev/badge/skills/goldziher/spikard/common-task-commands.svg" alt="Reviewed on agentmods" width="80" 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.00752 |
| Opus 5.5 | $0.00001 | $0.00301 |
| Sonnet 5.5 | $0.00001 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
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 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.
What it actually says
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)
Utilities:
task clean: Clean build artifactstask version:sync: Sync version from Cargo.toml to all manifests (package.json, pyproject.toml, pom.xml, go.mod, Gemfile, etc.)poly hooks run: Run poly's git hooks manuallytask pdfium:install: Download and install PDFium library
Alef Generation:
task alef:generate: Runalef all --clean --format=false; does not build bindings or format generated output- Do not add legacy aliases for build, Alef, or e2e workflows
What ships with it
1 file 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 Changed · -5 lines d86e88b106fd
- 13d ago Changed · +6 lines 10e39704d917
- 1mo 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 (123 stars, last pushed 4d ago), licensed MIT. It adds 3 tokens to every session and 752 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
python-patterns
Python development principles and decision-making. Framework selection, async patterns, type hints, and project structure.
tdd-cycle
Red-Green-Refactor TDD loop with mandatory false-positive check.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
deepagents-thread-inspector
Inspect and explain conversations in the local Deep Agents Code SQLite session store. Use to look up the current thread's title or name, as a fallback when LangSmith trace tooling is unavailable, for offline or untraced sessions, or when asked to identify or summarize a local dcode thread, inspect checkpoint metadata…
query-writing
Writes and executes SQL queries from simple SELECTs to complex multi-table JOINs, aggregations, and subqueries. Use when the user asks to query a database, write SQL, run a SELECT statement, retrieve data, filter records, or generate reports from database tables.