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 agentmods add skills/yc-software/qm/taste-skillnpx skills add yc-software/qm --skill taste-skillgit 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/taste-skill)<a href="https://agentmods.dev/skills/yc-software/qm/taste-skill"><img src="https://agentmods.dev/badge/skills/yc-software/qm/taste-skill.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.01070 |
| Opus 5 | $0.00025 | $0.00535 |
| Sonnet 5 | $0.00010 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
taste-skill 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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taste skill (design process for a browsable artifact)
Use this whenever you are about to build something a person will look at — a published
app or dashboard, a landing or status page, a prototype or deck. It carries the design
process; the anti-slop playbook in references/tasteskill.md carries the visual taste.
House style comes first
Unless the user asks for a different look, the default visual system is your
organization's house style: if the deployment installs a *-design skill (list
skills/), read it and apply its tokens — color, type, spacing, components. Depart from
it only when the user names a different brand or asks for a one-off exploration.
If the user wants a known brand's look (Stripe, Linear, Vercel, Notion…), read
skills/popular-web-designs/SKILL.md for the visual vocabulary and let this skill drive
the process.
The playbook
references/tasteskill.md is the full anti-slop playbook: read the brief before picking
an aesthetic, set the variance/motion/density dials, pick a real design system, and run
the pre-flight check before you call it done. Read it before you write markup for
anything externally facing or high-fidelity. Two adjustments for this runtime:
- The block library it describes (its Section 12) is a schema, not shipped files. There is
no
blocks/directory here — build the block and keep it in your workspace. - It targets landing pages, portfolios, and redesigns. For dense product UI, admin panels, and data tables, take its accessibility and anti-tell sections and leave the rest.
Runtime
You have a real computer, not a hosted design canvas. Build the artifact as files in your
workspace, verify it locally, and when it should outlive the turn ship it with the
publish skill (skills/publish/SKILL.md).
write/read/execute— author files, install deps, run build steps.background— run a dev server (PORT=8080 node server.js) so you can look at it.- local headless Chromium — confirm the page renders, the content is there, no console
errors, layout and links intact:
chromium --headless --no-sandbox --disable-gpu --dump-dom http://localhost:<port>(or--screenshot=/tmp/page.png, thenreadthe image). Nothing you baked in leaves the computer to be checked.
What ships with it
2 files 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.
- 5d ago First seen · 87 lines · 50 tokens per session scan A 3cafb80e638f
taste-skill is a skill published in the GitHub repository yc-software/qm (14,562 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,070 once invoked, about $0.0003 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-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…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
adding-a-provider-api-feature
Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
agent-initialization
Initialize an Agent's settings from a user requirement by writing AGENTS.md, setting identity metadata, and installing only needed Skills.
openclaw-ci-limits
Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe ramp-down/ramp-up changes. Use when tuning .github/workflows/, docs/ci.md, CI runner labels, matrix max-parallel…