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/i-stack/ai-coding-kit/engineering-disciplinenpx skills add i-stack/ai-coding-kit --skill engineering-disciplinegit clone --depth 1 https://github.com/i-stack/ai-coding-kitWhat 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.00062 | $0.00615 |
| Opus 5 | $0.00031 | $0.00308 |
| Sonnet 5 | $0.00012 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
engineering-discipline 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 yesterday.
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
Engineering Discipline
强制入口
命中本 skill 时，必须先完整阅读 references/engineering_discipline.md 并按其中条款执行。
- 不得以 preamble、Cursor 规则摘要或其它二次摘要代替该文件全文。
核心规则
- [GR-001] 绝对不读取、不打印、不提交任何敏感机密（.env、密钥、证书、API Token）；在调用可能改变系统状态或高风险的 shell 命令前，必须进行安全与授权自检，绝对不暴露 Credentials。
- [GR-002] 描述不清 / 上下文不足 / 歧义时，先以独立"前置确认"块字面输出 ≥1 个具体问题，不允许仅在散文里说"需要更多信息"。
- [GR-003] 默认先锁定 1 个最高概率根因或主路径，最多补充 1 个备选；不同时展开多个大分支。
- [GR-004] 默认按"根因 → 为什么 → 修法 → 验证"四段式输出；若任务命中长模板，四段式作为摘要层，详细模板作为附加层.
- [GR-005] 先给最小可验证修复，不先提出整模块重写、架构翻新或大范围重构。
- [GR-006] 限制工具调用深度与预算；当在同一修复/排障路径上连续失败 3 次，或单次任务工具调用深度（turn 数）超过 15 次时，必须主动中断、承认当前认知缺口，向用户进行战略前置确认。
- [GR-007] 不要格式化代码，除非明确要求格式化当前代码。执行自动修复或自动格式化工具时，范围必须局限于 Staged 变更内已修改的 lines，禁止无意引入大面积 Diff 噪声。
- [GR-008] 任何改动都必须声明"已覆盖、未覆盖、残留风险"三字段。
细则见 engineering_discipline.md。
何时加载
- 默认：所有工程类任务（含排障、设计、实现、审查）。
- 跳过：纯闲聊、无任何改动或判断成分的机械执行。
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 33 lines · 62 tokens per session scan A f096ef110400
engineering-discipline is a skill published in the GitHub repository i-stack/ai-coding-kit (3 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 615 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-31.
Other skills, from other repositories
extension-creator
Create AiderDesk extensions by setting up extension files, defining metadata, implementing Extension interface methods, and updating documentation. Use when building a new extension, creating extension commands, tools, or event handlers.
theme-factory
Create new AiderDesk UI themes by defining SCSS color variables, registering theme types, and adding i18n display names. Use when adding a theme, creating a color scheme, customizing appearance, or implementing dark mode and light mode variants.
agent-creator
Create and configure AiderDesk agent profiles by defining tool groups, approval rules, system prompts, subagent settings, subagent filtering, and provider/model selection. Use when setting up a new agent, creating a profile, or configuring agent tools, permissions, and subagent behavior.
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
ppt-design-skill
Design, generate, review, and revise editable PowerPoint presentations through a rigorous brief-to-PNG workflow using the public pptx-designer Python library.
githits-onboarding
Set up GitHits from an agent session: detect supported coding tools, install GitHits MCP configuration, start account sign-in/signup, verify auth, and recover from setup issues. Use when the user asks to install, connect, set up, sign up for, or start using GitHits.