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/kirodotdev/kirocrew/visual-editnpx skills add kirodotdev/KiroCrew --skill visual-editgit clone --depth 1 https://github.com/kirodotdev/KiroCrewWhat 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.00050 | $0.02336 |
| Opus 5 | $0.00025 | $0.01168 |
| Sonnet 5 | $0.00010 | $0.00467 |
| Haiku 4.5 | $0.00005 | $0.00234 |
Grade A, and why
visual-edit 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Edit — Design Tweak request handling
The Design Tweak app lets a designer visually pick element(s) in a live preview and attach natural-language comments. Comments accumulate into a request, and the designer sends the whole batch at once. One request file therefore contains many comments as sub-items:
~/.kiro/crew/apps/design-tweak/data/queue/<timestamp>-<id>.json
A request is a batch. Work every comment in it, and report per comment.
The loop
- Read the request file. The prompt names the request id; if not, read the
newest file in the queue dir.
statewill be"sent"— a"draft"request has not been handed to you yet, so leave drafts alone. - Work
comments[]in order. Each entry is an independent edit with its owncid,comment,sourceFile, andselection. Do not merge them into one change, even when two comments touch the same file. - For each comment, resolve the target, make the edit, and report against
that comment's
cid(see below). - When every comment is done, tell the user what changed, grouped by comment number.
Reporting progress — always per comment
Each comment has its own progress bubble in the preview, so notes must be
addressed to a cid:
POST /apps/design-tweak/api/thread?id=<requestId>&cid=<commentId>
body: {"role": "agent", "text": "Editing styles.css — uppercasing .section-title"}
Post one note when you start a comment, and one per meaningful step. Keep each to a single short line. When that comment is finished, post a final note carrying a status so its dot turns green:
POST /apps/design-tweak/api/thread?id=<requestId>&cid=<commentId>
body: {"role": "agent", "text": "Done — added text-transform: uppercase", "status": "done"}
The request's own status is derived: it flips to done on its own once every
comment is done. Never set it directly.
Never write to the request file yourself. Do not edit
state,status,sentAt, or any other field by writing the JSON — the panel derives the request's badge from its comments, and a hand-writtenstatedesynchronises them. Progress is reported only throughPOST /thread. The file is the app's state, not a scratchpad.
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.
- 2d ago First seen · 205 lines · 50 tokens per session scan A a12f9c710971
visual-edit is a skill published in the GitHub repository kirodotdev/KiroCrew (3,532 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 2,336 once invoked, about $0.0003 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-30.
Other skills, from other repositories
reskin
Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
concept-diagrams
Minimal SVG diagrams as standalone HTML files.
frontend-design
Create distinctive, production-grade frontend interfaces.
html-effectiveness
Generate self-contained, interactive HTML documents instead of markdown walls of text. When output is complex (comparisons, timelines, multi-option decisions, data tables, code reviews, diagrams), produce a single .html file that renders spatially and interactively in the browser. Zero dependencies, zero build steps.…
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…