io.github.aibenyclaude-coder/kira
NPM · KIRA-MCP · SCANNED AUG 3
Skills and Scars for AI agents - your agent records its failures and never repeats them.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to aibenyclaude-coder/Kira). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1911 tokens (~191/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · kira-mcp
claude mcp add aibenyclaude-coder-kira -- npx -y kira-mcp
codex mcp add aibenyclaude-coder-kira -- npx -y kira-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aibenyclaude-coder-kira": {
"type": "local",
"command": [
"npx",
"-y",
"kira-mcp"
],
"enabled": true
}
}
} openclaw mcp add aibenyclaude-coder-kira --command npx --arg -y --arg kira-mcp
mcp_servers:
aibenyclaude-coder-kira:
command: "npx"
args: ["-y", "kira-mcp"] {
"mcpServers": {
"aibenyclaude-coder-kira": {
"command": "npx",
"args": [
"-y",
"kira-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +53
- Malware scan: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: aibenyclaude-coder/Kira security
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 31 Jul 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 37
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- aibenyclaude-coder/Kira
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/aibenyclaude-coder/Kira/.github/workflows/release.yml@refs/tags/v0.8.1
- Rekor log index:
- 2082675708
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:f2eb132b7a82df2acbda64583cee947b0bba16c25f3ee695f01e3fc04878f974c70c98d501cf2ad5aea0173a04858e7bdd4a352dce5dcbb246a69a5b5
- Discovery method:
- attestation_endpoint
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
kira_consent ~109
Set the telemetry consent level for kira_report. level='off' disables all uploads (local log still written). level='basic' uploads only anonymous core (skill_id, status, anonymous UUID, version, OS family, Node major). level='full' additionally uploads sanitized free-text note/context. Call with no arguments to query the current state. See PRIVACY.md for the exact wire format and redaction rules.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | — | New consent level. Omit to query without changing. |
No output schema declared.
No examples provided.
kira_get ~96
Get the full instructions for a specific skill or scar by ID. Call this AFTER kira_lookup to retrieve the step-by-step instructions for the skill you've chosen. lookup returns summaries (no instructions) to save tokens — use this tool to get the full details.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The skill or scar ID (e.g., 'community.setup-stripe-nextjs.v1' or 'scar.vercel-env-vars-missing.v1'). |
No output schema declared.
No examples provided.
kira_lookup ~201
Look up skills (how to do it) AND scars (what to avoid) for a given keyword. Returns matching skills (community first, then vendor) and scars (critical first; your own recorded failures before shared ones, then by frequency). Personal scars recorded by kira_record_failure on this machine fire here too. The agent MUST: 1. Read ALL returned scars first — these are past failures. Avoid repeating them. 2. Read returned skills and choose the best fit for the project context. 3. ANNOUNCE the chosen skill's 'declaration' field to the user BEFORE executing. 4. Follow the skill's instructions step by step, watching for scar patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| context | array | — | Optional project context tags for disambiguation (e.g., ['nextjs', 'typescript']). |
| keyword | string | yes | The firing keyword or phrase (e.g., 'deploy vercel', 'add auth'). Case-insensitive. |
No output schema declared.
No examples provided.
kira_personal_brief ~203
Surface your most recent PERSONAL scars — the private, local-only failure notes recorded by kira_record_failure under ~/.kira/personal-scars/. Call this at the START of a session (ideally from a SessionStart hook) so you begin already aware of the walls you hit last time on this machine. Returns the top-N scars by recency (most recent first), each with its mistake and what to do instead. Pass 'limit' to change how many, and 'contexts' to keep only scars relevant to the current project. Personal scars are LOCAL-ONLY — this reads them from disk and never touches the network.
| Name | Type | Req | Description |
|---|---|---|---|
| contexts | array | — | Optional project context tags (e.g., ['nextjs', 'typescript']). When given, only scars sharing at least one context are returned; untagged scars are always kept (they apply everywhere). |
| limit | number | — | How many recent scars to return (default 5, max 50). |
No output schema declared.
No examples provided.
kira_premortem ~234
Run a PRE-MORTEM before starting a task. Given a goal (and optional project context), return a heat map of the past failure patterns (scars, shared and personal) most likely to bite — ranked by how many times each wall has been recorded (hit_count). Each hotspot includes the mistake, the fix ('instead'), a relative heat score, and estimated minutes saved by avoiding it, plus an aggregate prevention value. When nothing matches strictly, 'near_scars' lists the closest recorded scars instead. Call this FIRST for any non-trivial task to surface known traps up front, then read each hotspot's 'instead' and use kira_lookup / kira_route to plan the actual work.
| Name | Type | Req | Description |
|---|---|---|---|
| context | array | — | Optional project context tags (e.g., ['nextjs', 'typescript']) to focus the heat map. |
| goal | string | yes | The task you are about to start, in natural language (e.g., 'deploy a Next.js app to Vercel with Stripe'). |
| top_k | number | — | Max number of hotspots to return. Default 5, max 20. |
No output schema declared.
No examples provided.
kira_record_failure ~265
Capture a retry or exception you just hit as a PERSONAL scar — a private, local-only failure note stored under ~/.kira/personal-scars/. Call this immediately after a task needed extra attempts or threw an error, so future runs on this machine can avoid the same wall. Provide 'title' (what went wrong), 'mistake' (what was done / the exception), and ideally 'instead' (what to do next time). All free text is sanitized (keys, paths, emails redacted) before it touches disk. Personal scars are LOCAL-ONLY — they are never uploaded, on any tier.
| Name | Type | Req | Description |
|---|---|---|---|
| contexts | array | — | Project context tags (e.g., ['nextjs', 'typescript']). |
| instead | string | — | What to do instead next time (the fix / avoidance strategy). |
| keywords | array | — | Firing keywords so this scar surfaces on future lookups. |
| mistake | string | yes | What the agent did wrong, or the exception / retry cause. The pattern to recognize and avoid next time. |
| severity | string | — | Defaults to 'warning'. |
| summary | string | — | Optional one-line summary. Defaults to the title. |
| title | string | yes | Short summary of what went wrong (becomes the scar title). |
No output schema declared.
No examples provided.
kira_report ~180
Report the outcome of applying a Kira skill. ALWAYS call this after completing (or failing) a task guided by a Kira skill. Statuses: 'success' = worked first try, 'retry' = needed extra attempts, 'failure' = gave up. For 'retry' and 'failure', include a note describing what went wrong — this feeds the scar system so other agents don't repeat the same mistake.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | — | Optional sanitized snippet of agent context (project type, framework, etc.). Sent only when consent level is 'full'. |
| note | string | — | What went wrong (for retry/failure). This becomes a scar for future agents. Sent to the telemetry server only when consent level is 'full'. |
| skill_id | string | yes | The id of the skill that was applied. |
| status | string | yes | — |
No output schema declared.
No examples provided.
kira_route ~144
Plan a complete route for a goal. Instead of looking up individual skills, describe what you want to achieve (e.g., 'build a web app', 'add payments') and Kira returns an ordered sequence of steps, each with its Skill and Scars. Use this FIRST when the user describes a broad goal rather than a specific task. Then execute each step in order, calling kira_report after each one.
| Name | Type | Req | Description |
|---|---|---|---|
| context | array | — | Project context tags (e.g., ['nextjs', 'typescript']). |
| goal | string | yes | The user's goal in natural language (e.g., 'build a nextjs app', 'add payments', 'deploy my app'). |
No output schema declared.
No examples provided.
kira_share_scar ~153
Promote one of YOUR personal scars into a community submission so every Kira user stops hitting that wall. Takes a personal scar id (from kira_personal_brief / kira_lookup), re-sanitizes it, generalizes it to the community scar shape, and returns a prefilled GitHub issue URL plus a gh CLI fallback. NOTHING is uploaded by this tool — show the result to the user and let them submit. Accepted scars earn contributor status (see RECIPROCITY notes in the repo).
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | — | Target GitHub repo (default aibenyclaude-coder/Kira). |
| scar_id | string | yes | The personal scar to share (must start with 'scar.personal.'). |
No output schema declared.
No examples provided.
kira_status ~61
Report what's currently loaded and configured: kira version, tier (free/pro), telemetry consent level, counts of skills/scars/routes available, and where the local report log lives. Call this whenever you need to know the install state without exhausting the keyword search via lookup.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.