ckan-mcp-server: Command for Claude Code

.opencode/command/openspec-apply.md

openspec-apply is a command for Claude Code, OpenCode from ondata/ckan-mcp-server. It costs 12 tokens per session (325 once invoked), scanned A, original, MIT.

Implement an approved OpenSpec change and keep tasks in sync.

Command for Claude CodeOpenCode

Written for Claude Code and OpenCode: $ARGUMENTS substitution, but also installed under .opencode/. Also seen: mentions AGENTS.md.

This is ondata/ckan-mcp-server's own configuration. It tells Claude Code and OpenCode how to work on ckan-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ckan-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ondata/ckan-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ondata/ckan-mcp-server/main/.opencode/command/openspec-apply.md
Clone the repo
git clone --depth 1 https://github.com/ondata/ckan-mcp-server

Made for: Claude Code, OpenCode.

Wrote 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.

agentmods badge for openspec-apply

README.md
[![agentmods](https://agentmods.dev/badge/commands/ondata/ckan-mcp-server/openspec-apply.svg)](https://agentmods.dev/commands/ondata/ckan-mcp-server/openspec-apply)
Your own site
<a href="https://agentmods.dev/commands/ondata/ckan-mcp-server/openspec-apply"><img src="https://agentmods.dev/badge/commands/ondata/ckan-mcp-server/openspec-apply.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 325 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00325
Opus 5 $0.00006 $0.00162
Sonnet 5 $0.00002 $0.00065
Haiku 4.5 $0.00001 $0.00032

Measured today against content hash 9853692ac799, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

openspec-apply 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 today.

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.

.opencode/command/openspec-apply.md · 25 lines

What it actually says

The user has requested to implement the following change proposal. Find the change proposal and follow the instructions below. If you're not sure or if ambiguous, ask for clarification from the user. $ARGUMENTS

Guardrails

  • Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
  • Keep changes tightly scoped to the requested outcome.
  • Refer to openspec/AGENTS.md (located inside the openspec/ directory—run ls openspec or openspec update if you don't see it) if you need additional OpenSpec conventions or clarifications.

Steps Track these steps as TODOs and complete them one by one.

  1. Read changes/<id>/proposal.md, design.md (if present), and tasks.md to confirm scope and acceptance criteria.
  2. Work through tasks sequentially, keeping edits minimal and focused on the requested change.
  3. Confirm completion before updating statuses—make sure every item in tasks.md is finished.
  4. Update the checklist after all work is done so each task is marked - [x] and reflects reality.
  5. Reference openspec list or openspec show <item> when additional context is required.

Reference

  • Use openspec show <id> --json --deltas-only if you need additional context from the proposal while implementing.
Changes

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.

  1. today First seen · 25 lines · 12 tokens per session scan A 9853692ac799

Subscribe to this mod's changes

openspec-apply is a command published in the GitHub repository ondata/ckan-mcp-server (57 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 325 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-09-06.