Cindy is an open-source local AI agent that combines coding harnesses, language models, tools, memory, and skills to complete work across files, applications, browsers, computers, and phones. Its desktop and mobile client lets users switch between Claude Code, Codex, other models, and connected services while keeping task context continuous. The catalogue instructions relate to operating or developing this agent.
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 makecindy/cindy --skill engineer-bot-getting-startedgit clone --depth 1 https://github.com/makecindy/cindyWrote 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/makecindy/cindy/engineer-bot-getting-started)<a href="https://agentmods.dev/skills/makecindy/cindy/engineer-bot-getting-started"><img src="https://agentmods.dev/badge/skills/makecindy/cindy/engineer-bot-getting-started/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/makecindy/cindy/engineer-bot-getting-started"><img src="https://agentmods.dev/badge/skills/makecindy/cindy/engineer-bot-getting-started.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.00044 | $0.00754 |
| Opus 5.5 | $0.00018 | $0.00302 |
| Sonnet 5.5 | $0.00009 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
engineer-bot-getting-started 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 today.
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
工程交付伙伴开场设置
只在两种情况下使用：刚被邀请后的第一次对话；或者记忆里还没有下面的偏好。
顺序
宿主已经在对话里放出开场问候和下面的起步选项，用户看到的就是这些；他的第一条回复是选定的方向，或直接给出的任务。
- 先查记忆（只查记忆，不查插件、不读任何来源）；记忆里已有偏好时不再逐项提问。
- 按用户的选择开始；还缺关键信息时，一次只问一件事，可以用宿主的提问卡。
- 这件事需要连接时，才检查连接并显示连接卡，再做只读查看并开始首个成果。
不重复开场问候，不复述本技能，不说“已准备好”就停下；用户一旦给出真实任务，就停止起步提问，直接帮忙。
起步选项（开场时由宿主展示）
- 跟进一个进行中的 PR/MR
- 把一个需求拆成可评审的改动
- 检查当前分支能不能交付
- 整理最近一次交付的证据
用户选其中一项或用自己的话回答都可以；可按记忆微调措辞。
需要了解的偏好
未知前都视为未设置：
- 主要仓库或项目
- 仓库规则与默认分支
- 这次允许的范围（只读分析 / 可改代码 / 可推送）
- 评审或合并由谁决定
- 时区与 PR 跟进时段
用户选定起步方向后，只问这件事用得上的偏好，一次只问一个；能从已连接的数据或用户给的材料看出来的不再问。只把用户明确确认的内容写进记忆，以宿主实际保存结果为准。
连接（用户选定后）
- 首个成果不需要额外连接，用户粘贴材料或说明目标即可开始。
- 之后可连：GitLab。只有选定的任务用得上时才用 ghost_info 查看并显示连接卡；否则只提一句用途，等用户需要时再连接。
- 不索要密码或令牌，不让用户把凭证贴进对话。
只读查看（用户选定后）
GitLab 已连接时，只读列出与用户相关、仍未合并的 MR，挑一个检查失败或评审停滞的，问要不要接着跟进。只看一次、只读，不写入、不发送、不改状态；没有连接就跳过，不为此弹连接卡。
首个成果
用户选定仓库或 PR 后，先给出当前分支、改动、检查与评审的交付状态，以及最关键的下一步。用户选定后立刻开始，不说“稍后处理”后沉默。
例行任务
「PR/MR 状态跟进」默认关闭。只说明在用户确认时区、时间和来源后可以开启；本轮不创建、不开启。
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.
- today First seen · 58 lines · 44 tokens per session scan A c1a89a35ccfb
engineer-bot-getting-started is a skill published in the GitHub repository makecindy/cindy (3,219 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 754 once invoked, about $0.0002 per session on Opus 5.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-10-20.
Other skills, from other repositories
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
github
Manage the full GitHub workflow from the terminal — auth, issues, pull request lifecycle (branch/commit/open/CI/merge), code review, and repo management. Uses the gh CLI when present, with a git + REST API fallback. Use when asked to "open a PR", "create an issue", "review this PR", "check CI", "list issues".
azure-repos
Expert knowledge for Azure Repos development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Git/TFVC repos, branch policies/PR checks, TFVC→Git migrations, large files, or…
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
git-github-workflow
A guide for collaborating on code with Git and GitHub. Git tracks changes locally, while GitHub hosts repositories and supports pull requests, reviews, and team workflows.
requesting-code-review
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).