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 No-Compromise-AI/glm-mcp --skill backlog-to-issuegit clone --depth 1 https://github.com/No-Compromise-AI/glm-mcpWrote 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/no-compromise-ai/glm-mcp/backlog-to-issue)<a href="https://agentmods.dev/skills/no-compromise-ai/glm-mcp/backlog-to-issue"><img src="https://agentmods.dev/badge/skills/no-compromise-ai/glm-mcp/backlog-to-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/no-compromise-ai/glm-mcp/backlog-to-issue"><img src="https://agentmods.dev/badge/skills/no-compromise-ai/glm-mcp/backlog-to-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.00114 | $0.01660 |
| Opus 5 | $0.00057 | $0.00830 |
| Sonnet 5 | $0.00023 | $0.00332 |
| Haiku 4.5 | $0.00011 | $0.00166 |
Grade A, and why
backlog-to-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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/backlog-to-issue — make a backlog item delegable
A PostMQ backlog item is written mid-session, for a human, by someone who had the whole context in their head. A GLM agent has none of that. It gets the issue text and a repository, and everything the item left implicit becomes something it has to guess.
This skill closes that gap. In: a backlog item. Out: a GitHub issue glm-drain -i <n> can
work, and a backlog item that points at it.
It is a triage step, not a formatting step. Some items should not become issues at all.
1. Read the item, and its neighbours
mcp__postmq__get_backlog_item for the item. Then, before writing anything:
mcp__postmq__query_decisionsfor anything touching the same area — an item often restates a problem a decision already settled, or contradicts one.mcp__postmq__query_applicable_ruleswith the paths you expect to touch.- Existing GitHub issues. A duplicate issue is worse than no issue: two agents will work it.
2. Triage — decide what this item IS
Not every item is ready. Pick one, and say which:
| verdict | when | what to do |
|---|---|---|
| Ready | one behaviour changes, and you can name what "working" looks like | write the issue |
| Too big | more than one behaviour, or "and" in the title | split into several issues, each independently shippable and verifiable |
| Underspecified | you cannot write a done-when without guessing | ASK the user. Do not invent the missing half |
| Already done | the code already does it | resolve the backlog item with closing notes; write no issue |
| Not a code change | a decision, a question, a policy | it belongs in the decision log, not an issue |
Underspecified is the common one and the expensive one. An agent handed an ambiguous spec does not stop — it picks an interpretation and builds it, and you find out after review. If you cannot state the done-when, the item is not ready and asking costs a minute.
3. Ground it in the actual code
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.
- 10d ago First seen · 145 lines · 114 tokens per session scan A 3f5e857de2ed
backlog-to-issue is a skill published in the GitHub repository No-Compromise-AI/glm-mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 114 tokens to every session and 1,660 once invoked, about $0.0006 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
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.