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 mindspore-ai/akg --skill akg-issuegit clone --depth 1 https://github.com/mindspore-ai/akgWrote 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/mindspore-ai/akg/akg-issue)<a href="https://agentmods.dev/skills/mindspore-ai/akg/akg-issue"><img src="https://agentmods.dev/badge/skills/mindspore-ai/akg/akg-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/mindspore-ai/akg/akg-issue"><img src="https://agentmods.dev/badge/skills/mindspore-ai/akg/akg-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 Data Exfiltration · line 362 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 362 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 381 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00071 | $0.03393 |
| Opus 5 | $0.00036 | $0.01697 |
| Sonnet 5 | $0.00014 | $0.00679 |
| Haiku 4.5 | $0.00007 | $0.00339 |
Grade A, and why
akg-issue scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "https://api.gitcode.com/api/v5/repos/<owner>/<repo>/issues?access_token=$GITCODE_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AKG Issue 生成
⛔ 核心规则
- 所有产物写入
$AKG_AGENTS_DIR/.tmp/issue/，禁止写入其他位置。 - Issue 模板格式已内嵌在本文档 Step 3a 中，无需读取外部文件，直接使用下方模板。
- 所有 Issue 标题必须带
[AKG_AGENTS]前缀。 - 生成完成后必须执行规范校验。
- API 提交仅在用户选择后执行。
- 禁止在 shell 中打印 Token 值。检查 Token 是否存在只能用
[ -z "$VAR" ]判断。 - owner 和 repo 必须从
git remote -v的 URL 提取，禁止从用户输入的分支名推断。
流程总览
Step 0 模式判定（自动）
Step 1 收集信息（自动 / 交互）
Step 2 检测远程信息（自动）
Step 3 生成 Issue 文件（自动）
Step 4 规范校验（自动）
Step 5 展示结果 + 用户决策（一次交互）
Step 6 执行 API 提交（仅当用户选择"提交"时，不再二次确认）
Step 0: 模式判定
解析 $ARGUMENTS，判定使用哪种模式：
Diff 模式触发条件（满足任一）：
- 输入包含"分支""diff""对比""比较""差异""branch"等关键词
- 输入格式为"从 A 到 B"或"A → B"
- 用户明确要求基于代码变更/提交生成 issue
描述模式：不满足以上条件的所有情况。
Step 1: 收集信息
Diff 模式
目标分支解析：从用户输入中提取目标分支名。用户输入的分支名直接作为 git diff 的目标 ref 使用，例如：
- 用户说"origin/master" →
git diff origin/master...HEAD - 用户说"master" →
git diff master...HEAD
⚠️ 分支名仅用于 git diff/log 命令。不要从分支名推断 owner、repo 或平台信息。
git rev-parse --abbrev-ref HEAD
git diff <target_ref>...HEAD --stat
git log <target_ref>..HEAD --oneline --no-merges
git diff <target_ref>...HEAD
无差异 → 报错终止。
基于 diff 自动推断（不需要向用户询问）：
| 字段 | 推断逻辑 |
|---|---|
issue_type |
代码变更类型：bug fix 相关 → bug，新功能 → task，大规模设计/重构 → rfc |
title |
[AKG_AGENTS] <概要描述> |
labels |
["kind/<issue_type>"] |
body |
按对应模板格式生成，描述本分支做了什么、要解决什么问题 |
描述模式
从 $ARGUMENTS 中提取信息：
| 信息 | 提取方式 |
|---|---|
issue_type |
用户明确指定 → 直接用。否则推断：报错/crash/失败 → bug，需求/设计/方案 → rfc，其他 → task |
title |
从描述提炼一句话摘要，加 [AKG_AGENTS] 前缀 |
body |
按模板格式组织用户描述 |
如果用户未指定 issue_type 且无法推断，使用 question 工具一次性询问：
请选择 Issue 类型：
- Bug Report — 报告一个 bug
- RFC — 提出新功能或增强方案
- Task — 跟踪一项任务
Bug 类型额外采集环境信息（自动执行）：
cat $HOME_DIR/.akg/check_env.md 2>/dev/null
uname -a
python3 --version 2>/dev/null || python --version
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.
- 9d ago First seen · 404 lines · 71 tokens per session scan A f8e2fa7d0fc9
akg-issue is a skill published in the GitHub repository mindspore-ai/akg (259 stars, last pushed 29d ago), licensed Apache-2.0. It adds 71 tokens to every session and 3,393 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.