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 openyida/openyida-openclaw-skill --skill yida-issuegit clone --depth 1 https://github.com/openyida/openyida-openclaw-skillWrote 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/openyida/openyida-openclaw-skill/yida-issue)<a href="https://agentmods.dev/skills/openyida/openyida-openclaw-skill/yida-issue"><img src="https://agentmods.dev/badge/skills/openyida/openyida-openclaw-skill/yida-issue/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/openyida/openyida-openclaw-skill/yida-issue"><img src="https://agentmods.dev/badge/skills/openyida/openyida-openclaw-skill/yida-issue.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.00082 | $0.00403 |
| Opus 5.5 | $0.00033 | $0.00161 |
| Sonnet 5.5 | $0.00016 | $0.00081 |
| Haiku 4.5 | $0.00008 | $0.00040 |
Grade A, and why
yida-issue 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 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.
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
一句话提需求
用自然语言描述需求，自动路由到正确仓库并创建 GitHub Issue。
路由规则
| 关键词/场景 | 目标仓库 |
|---|---|
| CLI、命令行、安装、CI/CD、贡献者、npm | openyida/openyida |
| 登录、创建应用/页面/表单、发布、Schema、宜搭 API | openyida/yida-skills |
| 无法判断 | 提示用户手动指定 --repo |
使用方式
node scripts/create-issue.js "<需求描述>" [--repo openyida|yida-skills] [--type feature|bug] [--dry-run]
前置依赖
- Node.js ≥ 16
- GitHub CLI（
gh）已安装并已登录（gh auth login）
使用示例
# 自动判断路由到正确仓库
node scripts/create-issue.js "希望支持批量导出表单数据"
# 手动指定仓库
node scripts/create-issue.js "CLI 新增 yida list 命令" --repo openyida
# 报告 bug
node scripts/create-issue.js "创建应用时图标颜色不生效" --type bug
# 预览模式（不实际创建）
node scripts/create-issue.js "希望支持 xxx" --dry-run
What ships with it
1 file 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.
- 2mo ago First seen · 44 lines · 82 tokens per session scan A 48025d5d8698
yida-issue is a skill published in the GitHub repository openyida/openyida-openclaw-skill (5 stars, last pushed 7mo ago), licensed MIT. It adds 82 tokens to every session and 403 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.