Borrowing it
Nothing to install: this file belongs to victoriacity/openakari. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/victoriacity/openakari/main/.claude/skills/develop/SKILL.mdgit clone --depth 1 https://github.com/victoriacity/openakariWrote 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/skills/victoriacity/openakari/develop)<a href="https://agentmods.dev/skills/victoriacity/openakari/develop"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/develop/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/victoriacity/openakari/develop"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/develop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.02031 |
| Opus 5.5 | $0.00007 | $0.00812 |
| Sonnet 5.5 | $0.00003 | $0.00406 |
| Haiku 4.5 | $0.00002 | $0.00203 |
Grade A, and why
develop scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: ["Read", "Grep", "Glob", "Edit", "Write", "Bash(cd infra/scheduler && npm test)", "Bash(cd infra/scheduler && npx tsc --noEmit)", "Bash(cd infra/scheduler && npm run build)", "Bash(cd infra/scheduler && np How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/develop
Develop akari infrastructure code using test-driven development. Covers new features and bug fixes in infra/.
The argument determines the mode:
| Argument pattern | Mode | Example |
|---|---|---|
fix <description> |
Bugfix | /develop fix living message shows no final text |
| Anything else | Feature | /develop mid-run message forwarding via streamInput |
Mode: Feature
Step 1: Understand
- Read the relevant source files in
infra/scheduler/src/. - Check
decisions/for constraints on the area you're changing. - Search for existing patterns — functions, types, utilities — that can be reused. Do not build what already exists.
- Config and access patterns: When encountering "not configured" or "unavailable" errors, check:
infra/*/docs/for documented patterns (e.g.,provider-quirks.mdfor API key BYOK)- Other projects' logs and experiments via
grep -r "<capability>" projects/ decisions/for constraints on credentials and access
- If the scope is large (>3 files, architectural change), use
EnterPlanModeto plan first.
Step 2: Write tests
- Identify the test file — colocated as
<module>.test.tsnext to the source file. - Write failing tests that describe the expected behavior. Cover:
- Happy path (the feature works as intended)
- Edge cases (empty inputs, missing data, error conditions)
- Integration points (does it interact correctly with adjacent modules?)
- Run tests to confirm they fail:
cd infra/scheduler && npm test
Step 3: Implement
- Write the minimum code to make tests pass.
- Follow existing patterns in the codebase (naming, error handling, types).
- Keep files under ~150 lines. Extract new modules if needed.
- Run tests after each significant change:
cd infra/scheduler && npm test
Step 4: Verify
- All tests pass:
cd infra/scheduler && npm test - Type check passes:
cd infra/scheduler && npx tsc --noEmit - No unintended side effects — review your diff with
git diff.
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.
- 2mo ago First seen · 180 lines · 17 tokens per session scan A 69d0ac926e46
develop is a skill published in the GitHub repository victoriacity/openakari (47 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 2,031 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…