QM is a shared work environment for coding agents that gives each employee and conversation an isolated workspace while allowing collaboration in Slack and on the web. Startups use it to run agents for individuals, teams, and company operations, with selectable harnesses and models. The catalogue entries extend QM with skills, instructions, and settings.
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 yc-software/qm --skill github-gitlabgit clone --depth 1 https://github.com/yc-software/qmWrote 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/yc-software/qm/github-gitlab)<a href="https://agentmods.dev/skills/yc-software/qm/github-gitlab"><img src="https://agentmods.dev/badge/skills/yc-software/qm/github-gitlab/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/yc-software/qm/github-gitlab"><img src="https://agentmods.dev/badge/skills/yc-software/qm/github-gitlab.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 Excessive Agency · line 16 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 21 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00025 | $0.01386 |
| Opus 5.5 | $0.00010 | $0.00554 |
| Sonnet 5.5 | $0.00005 | $0.00277 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
github-gitlab 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 3d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub / GitLab
Use this skill when the user asks to inspect repos, issues, pull requests, merge requests, code history, branches, or to make a small code change in a hosted repo.
Choose the account deliberately
Use the current credential manifest to choose an account authorized for this conversation
that fits the user's intent. Run commands with execute and an explicit sandbox_id;
keep that ID throughout checkout, edits, checks, and push. Personal and shared accounts are both valid choices; neither
is an automatic fallback when the other fails. If the intended account is unclear before
a write, ask. Do not infer permission from a login merely being present on the computer.
- Personal login: use the authorized
gh,glab, or Git login. Check the active provider account (for example,gh api user --jq .login) and the Git transport's auth configuration; a CLI API identity alone does not prove which account Git will use. - Shared org credential: if listed in the prompt, select its slug and use the
core-hosted smart HTTP remote in the
use-shared-credentialskill. This uses the configured shared account, even when a personal OAuth connector is live. Its name is an admin label, not a verified upstream username. - Connected app: use only advertised capabilities. API access does not by itself establish native Git transport access or configure the CLI's active login.
For an existing checkout, inspect the remote and applicable credential-helper, SSH, proxy, and HTTP-header configuration. A reused checkout may still select a previous account. Commit author metadata is separate from transport identity. Resolve an unknown identity before a write; do not probe access by pushing.
Logging in
Use the native login only after an explicit authentication rejection. A TLS timeout, connection reset, rate limit, or GitHub server error is not evidence of logout or permission expiry. Do not consume another credential grant to repair transport.
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.
- 3d ago Changed · +3 lines 686bc05e7520
- 7d ago Changed · -10 lines 26b40055d64c
- 27d ago Changed 22c998ef528f
- 28d ago Changed · -1 lines 74aabfba14b1
- 29d ago Changed · +42 lines 914965542054
- 1mo ago Changed 4349ce1a6c35
- 1mo ago Changed · +13 lines dcf4aac9f784
- 1mo ago First seen · 99 lines · 25 tokens per session scan A 17de274d57f8
github-gitlab is a skill published in the GitHub repository yc-software/qm (15,434 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 1,386 once invoked, about $0.0001 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-30.
Other skills, from other repositories
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
gh-issues
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
github
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
diffs
Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.