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/amonstack/gitea_mcp/gitea-comment-issuenpx skills add amonstack/gitea_mcp --skill gitea-comment-issuegit clone --depth 1 https://github.com/amonstack/gitea_mcpWhat 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.00090 | $0.00452 |
| Opus 5 | $0.00045 | $0.00226 |
| Sonnet 5 | $0.00018 | $0.00090 |
| Haiku 4.5 | $0.00009 | $0.00045 |
Grade A, and why
gitea-comment-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 2d 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.
What it actually says
gitea-comment-issue
Post one new comment that advances an issue's discussion. Tools: get_issue, create_comment.
Prerequisites
- Resolve
owner+repo: pass explicitly, elseGITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, elseresolve_repo(gitea-resolve-repo). Never guess — wrong values post to the wrong place. index= the issuenumber(URL #N → N), never the internalid.
Flow
- CONFIRM TARGET:
get_issue({ index })— verify the issue exists and is the one you mean. Do NOT post blind. - POST:
create_comment({ index, body }).
create_comment
- RULES:
bodyrequired, Markdown. The comment APPENDS to the thread — it never edits or replaces prior content. The response carries the commentid; retain it only if a follow-upupdate_comment/delete_commentis planned. - CHECK FIRST: re-read the latest thread (gitea-summarize-issue) so your comment is not redundant or contradicting a newer message.
- CHECK AFTER: the comment appears with the returned
id.
Body template — standardize what you write into body
A useful comment is contextual, evidence-backed, and proposes a next step. Structure body with this template; drop sections that add nothing.
**Context:** <the point you are responding to>
**Finding / proposal:** <what you discovered or suggest>
**Evidence:** <log excerpt, link, reproduction, or metric>
**Suggested next step:** <the concrete action you propose>
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.
- 2d ago First seen · 35 lines · 90 tokens per session scan A 6dfe74647b2a
gitea-comment-issue is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 9d ago), licensed MIT. It adds 90 tokens to every session and 452 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…