code-implementor

An implementation skill for completing planned code changes and preparing them for verification. Verification is the process of running tests and other configured checks to confirm the change works.

In plain words
What is it for?
Use it to run or arrange tests, check the OpenLogos test reporter, inspect verification settings, and add a suitable test command when the project's technology makes one clear.
Why use it?
It catches missing test results and missing verification commands before delivery, reducing the chance that a partial test run gives a false sense of completion.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/miniidealab/openlogos/code-implementor
Any agent
npx skills add miniidealab/openlogos --skill code-implementor
Clone the repo
git clone --depth 1 https://github.com/miniidealab/openlogos

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 396 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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 $0.00000 $0.00396
Opus 5 $0.00000 $0.00198
Sonnet 5 $0.00000 $0.00079
Haiku 4.5 $0.00000 $0.00040

Measured 2d ago against content hash 77cb1ea434b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-implementor 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.

logos/changes/archive/20260527-1921-verify-pre-run-regression-and-incremental-tests/deltas/skills/code-implementor/SKILL.md · 30 lines

What it actually says

MODIFIED — Step 6: 完成后引导用户运行 verify

Step 6: 完成后引导用户运行 verify

代码实现完成后,AI 必须:

  1. 确认测试结果:运行或提示运行对应测试,确保 logos/resources/verify/test-results.jsonl 或配置的阶段结果文件已生成。
  2. 检查 reporter:所有本批新增 / 修改的 UT/ST 测试必须写入 OpenLogos reporter。
  3. 检查 verify 预跑配置:读取 logos/logos.config.json,确认至少存在一个字段:
    • verify.pre_run_command
    • verify.regression_command
    • verify.incremental_command
  4. 自动补齐或明确诊断
    • 若项目已有配置,不覆盖。
    • 若缺失且可从技术栈推断,则写入 verify.pre_run_command
    • 若无法推断,必须在交付说明中明确提示用户补充配置,不能只说“建议配置”。
  5. 解释原因:reporter 可能在测试运行时清空 JSONL;如果只运行局部测试,openlogos verify 会因覆盖不足失败。预跑配置是代码完成前检查项,不是可选建议。

默认推断规则:

技术栈 / 文件 默认命令
package.json 存在 scripts.test npm test
Vitest npx vitest run
Jest npx jest
pytest pytest
Go go test ./...
Cargo cargo test

若用户明确选择两阶段策略,可写入 verify.regression_commandverify.incremental_command,并确保阶段结果不会相互覆盖。

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. 2d ago First seen · 30 lines · 0 tokens per session scan A 77cb1ea434b2

Subscribe to this mod's changes

code-implementor is a skill published in the GitHub repository miniidealab/openlogos (71 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 396 tokens. 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens