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/ostin-pil/aboard/commitnpx skills add ostin-pil/aboard --skill commitgit clone --depth 1 https://github.com/ostin-pil/aboardWhat 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.00013 | $0.00514 |
| Opus 5 | $0.00006 | $0.00257 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
commit 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.
What it actually says
Commit pending changes using the project convention: prefix(topic): short description
Arguments
- No arguments: auto-generate the commit message from the diff
$ARGUMENTSprovided: use it as the commit message (must still follow convention)
Process
- Run
git status(never use-uall) andgit diffto see all pending changes - Exclude these from staging — never commit them:
.env,credentials.json, secretsnode_modules/,.next/,out/,build//tmp/debug logs, scratch files.DS_Store
- Stage all remaining changed/new files with
git add <file>...(list files explicitly, nevergit add -A) - If
$ARGUMENTSis provided, use it as the commit message. Otherwise, analyze the diff and generate one:- Prefix — infer from the nature of the change:
feat— new feature or capabilityfix— bug fixdocs— documentation, session logs, researchchore— config, scripts, tooling, dependencies
- Topic — the area of the codebase, e.g.:
claims,graph,dossier,forecast,schema,jsonld,ui,data,lib,scripts,research,sessions,config,deps,claude - Description — concise, lowercase, under 72 chars total, focuses on "why" not "what"
- Prefix — infer from the nature of the change:
- Commit using a HEREDOC (no
Co-Authored-Bytrailer, ever):git commit -m "$(cat <<'EOF' prefix(topic): short description EOF )" - Report: show the commit hash and full message
Rules
- One logical change per commit — if changes span unrelated areas, ask the user to split
- Title must be under 72 characters
- Never add
Co-Authored-Bytrailers - Never use
git add -Aorgit add . - If there are no changes to commit, say so and stop
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 · 47 lines · 13 tokens per session scan A 44f397099f4d
commit is a skill published in the GitHub repository ostin-pil/aboard (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 514 once invoked, about $0.0001 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
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.