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.
/plugin marketplace add hesedcasa/sdkcknpx agentmods add plugins/hesedcasa/sdkck/apigit clone --depth 1 https://github.com/hesedcasa/sdkckWrote 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/plugins/hesedcasa/sdkck/api)<a href="https://agentmods.dev/plugins/hesedcasa/sdkck/api"><img src="https://agentmods.dev/badge/plugins/hesedcasa/sdkck/api.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
api 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
{
"name": "api",
"description": "Extract API endpoints from GitHub repos, online docs, or local files and import them as sdkck CLI commands",
"source": "./plugins/api",
"strict": false,
"category": "productivity"
}What it installs
The manifest is a name and a version. 1 skill, 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 139 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#api 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.
- yesterday First seen · 7 lines scan A 34bc7426339f
api is a plugin published in the GitHub repository hesedcasa/sdkck (9 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
bkt
Bitbucket CLI - manage repos, PRs, branches, issues, webhooks, and pipelines for both Data Center and Cloud.
fullstack-dev-kit
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
allbeads
Multi-repo orchestration for AI agent workflows. Aggregate beads across repositories, manage contexts, and coordinate distributed work.
workingon
Claude Code skill and hooks that record your work in Jira, Linear, GitHub Issues, Trello or Vikunja.
dev-day
The complete developer day-loop for Claude Code + Jira: /start-session boots a senior-collaborator session (feedback memory, Jira backlog, standing plan-gate), /standup answers 'anything pending?', /bug-triage root-causes tickets, /groom preps them for estimation, /create-ticket files them, /jira-comment posts clean…
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.