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 skills add miniidealab/openlogos --skill code-implementorgit clone --depth 1 https://github.com/miniidealab/openlogosWrote 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/miniidealab/openlogos/code-implementor)<a href="https://agentmods.dev/skills/miniidealab/openlogos/code-implementor"><img src="https://agentmods.dev/badge/skills/miniidealab/openlogos/code-implementor/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/miniidealab/openlogos/code-implementor"><img src="https://agentmods.dev/badge/skills/miniidealab/openlogos/code-implementor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 23 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 24 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00000 | $0.00396 |
| Opus 5.5 | $0.00000 | $0.00158 |
| Sonnet 5.5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 1mo 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.
What it actually says
MODIFIED — Step 6: 完成后引导用户运行 verify
Step 6: 完成后引导用户运行 verify
代码实现完成后，AI 必须：
- 确认测试结果：运行或提示运行对应测试，确保
logos/resources/verify/test-results.jsonl或配置的阶段结果文件已生成。 - 检查 reporter：所有本批新增 / 修改的 UT/ST 测试必须写入 OpenLogos reporter。
- 检查 verify 预跑配置：读取
logos/logos.config.json，确认至少存在一个字段：verify.pre_run_commandverify.regression_commandverify.incremental_command
- 自动补齐或明确诊断：
- 若项目已有配置，不覆盖。
- 若缺失且可从技术栈推断，则写入
verify.pre_run_command。 - 若无法推断，必须在交付说明中明确提示用户补充配置，不能只说“建议配置”。
- 解释原因：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_command 与 verify.incremental_command，并确保阶段结果不会相互覆盖。
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.
- 1mo ago First seen · 30 lines · 0 tokens per session scan A 77cb1ea434b2
code-implementor is a skill published in the GitHub repository miniidealab/openlogos (322 stars, last pushed 4d 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.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.