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 cyanheads/workflows-mcp-server --skill report-issue-frameworkgit clone --depth 1 https://github.com/cyanheads/workflows-mcp-serverWrote 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/cyanheads/workflows-mcp-server/report-issue-framework)<a href="https://agentmods.dev/skills/cyanheads/workflows-mcp-server/report-issue-framework"><img src="https://agentmods.dev/badge/skills/cyanheads/workflows-mcp-server/report-issue-framework/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/cyanheads/workflows-mcp-server/report-issue-framework"><img src="https://agentmods.dev/badge/skills/cyanheads/workflows-mcp-server/report-issue-framework.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.00052 | $0.03115 |
| Opus 5.5 | $0.00021 | $0.01246 |
| Sonnet 5.5 | $0.00010 | $0.00623 |
| Haiku 4.5 | $0.00005 | $0.00312 |
Grade A, and why
report-issue-framework 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 15d 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.
This is a copy
100% identical to report-issue-framework — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
You've isolated a problem to @cyanheads/mcp-ts-core itself — not your server code, not a misconfiguration, not a missing peer dependency. Typical triggers:
- Framework builder (
tool(),resource(),prompt()) rejects valid input or produces incorrect output createApp()orcreateWorkerHandler()fails on a valid configContextproperties (ctx.log,ctx.state,ctx.inputs, etc.) behave contrary to docs- A utility from
/utils,/errors,/auth,/storage,/servicesreturns wrong results or throws unexpectedly - Type exports are incorrect or missing (compile error on documented usage)
- The definition linter (
bun run lint:mcp) produces false positives or misses real violations
For general gh CLI workflows outside issue filing (PRs, workflows, API access), see the github-cli skill.
Before Filing
- Confirm framework version —
bun pm ls @cyanheads/mcp-ts-coreor checknode_modules/@cyanheads/mcp-ts-core/package.json - Check you're on latest —
bun outdated @cyanheads/mcp-ts-core. If behind, update and retest before filing. - Isolate the issue — reproduce with a minimal handler or standalone script. Strip server-specific services, config, and dependencies. If the bug disappears when isolated, it's likely in your server code.
- Search existing issues — don't file duplicates:
gh issue list -R cyanheads/mcp-ts-core --search "your error message or keyword" --state all
# Assess a close match before commenting — is it already linked to a fix or referenced elsewhere?
gh issue view <number> -R cyanheads/mcp-ts-core # body
gh issue view <number> -R cyanheads/mcp-ts-core --comments # thread only — without a TTY it prints no body
gh api 'repos/cyanheads/mcp-ts-core/issues/<number>/timeline' --paginate \
--jq '.[] | select(.event=="cross-referenced") | .source.issue | "\(.repository.full_name)#\(.number) — \(.title)"'
- For documentation- or contract-shaped requests, audit all three doc layers first — proposals to add reference docs, public-API conventions, attribute/event catalogs, or stability commitments often duplicate surface that already exists. Check
src/for behavior,docs/for human-facing reference, andframework-skills/for agent-facing reference. Skill files markedaudience: externalare the framework's public contract — treat them as authoritative when evaluating whether a documentation gap exists. Also verify the constants or types you'd reference aren't already exported from@cyanheads/mcp-ts-coreor one of its subpaths.
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.
- 15d ago Changed · +2 lines e117f3333d07
- 1mo ago Changed · -28 lines 01825e7c3144
- 1mo ago Changed c5ff8a604f85
- 1mo ago First seen · 301 lines · 52 tokens per session scan A 257a59da6a7e
report-issue-framework is a skill published in the GitHub repository cyanheads/workflows-mcp-server (31 stars, last pushed 16d ago), licensed Apache-2.0. It adds 52 tokens to every session and 3,115 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to report-issue-framework, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
browser-testing-with-devtools
Verify browser behavior with runtime evidence from DOM, console, network, and performance signals.
debugging-and-error-recovery
Reproduce, localize, reduce, fix, and guard failures without guessing or masking errors.
test-workflow
Universal n8n workflow testing via webhook or sub-workflow pattern.
monitor-executions
Monitor n8n workflow executions. Wait for completion, extract output, get errors, list failed runs. Use for execution tracking and debugging.
n8n-diagnostics
Diagnose n8n issues by analyzing logs, detecting error patterns, and providing actionable fixes. Use when workflows fail, services are unhealthy, or debugging n8n problems.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.