agentmods.dev

gitea-write-wiki

A tool for creating, editing, and reorganising pages in a Gitea repository wiki. A repository wiki is a set of documentation pages attached to a code project.

In plain words
What is it for?
Use it to survey existing pages, create or update documentation, follow the repository's Markdown format, and add pages to the sidebar or home index.
Why use it?
It helps keep wiki pages consistent, avoids duplicate pages, and makes new pages reachable through the wiki navigation.

Skill for Claude CodeCodex

1 9d ago A scan 89 tokens original MIT
View the source file amonstack/gitea_mcp
Install

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.

agentmods
npx agentmods add skills/amonstack/gitea_mcp/gitea-write-wiki
Any agent
npx skills add amonstack/gitea_mcp --skill gitea-write-wiki
Clone the repo
git clone --depth 1 https://github.com/amonstack/gitea_mcp

Made for: Claude Code, Codex.

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 866 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00089 $0.00866
Opus 5 $0.00044 $0.00433
Sonnet 5 $0.00018 $0.00173
Haiku 4.5 $0.00009 $0.00087

Measured 2d ago against content hash 0fb9c33b7440, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitea-write-wiki 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.

src/assets/skills/gitea-write-wiki/SKILL.md · 36 lines

How it starts

The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gitea-write-wiki

Create or edit wiki pages following mainstream open-source conventions (Gitea/GitHub wiki model + GitLab-derived Markdown style). Tools: list_wiki_pages, get_wiki_page, create_wiki_page, update_wiki_page, list_wiki_revisions.

Prerequisites

  • Resolve owner+repo: pass explicitly, else GITEA_DEFAULT_OWNER/GITEA_DEFAULT_REPO, else resolve_repo (gitea-resolve-repo).
  • The repo's wiki feature must be enabled — the endpoints return 404 otherwise.
  • There is NO optimistic locking — always read a page before overwriting it.

Flow

  1. SURVEY (always first): list_wiki_pages({}). Decide create vs update; check for near-duplicate titles to merge into instead of creating a parallel page.
  2. READ (edit only): get_wiki_page({ pageName }) — never blind-overwrite; base the edit on the current content.
  3. WRITE: create_wiki_page({ title, content, message? }) or update_wiki_page({ pageName, content?, message? }), with content formatted per format-guide.md (bundled next to this file — read it before writing).
  4. LINK: a page nobody can navigate to is a lost page. Add new pages to the _Sidebar navigation (and the Home index when the wiki is curated there) via update_wiki_page({ pageName: "_Sidebar", ... }).
  5. ALWAYS pass a message (commit message) summarizing the change — the wiki is a git repo and the history is the audit trail.

Tool rules

  • pageName / title are the page title as it appears in the wiki URL (Home, Getting-Started) — hyphenated, no .md suffix, no spaces.
  • create_wiki_page FAILS if the title already exists — that is the signal to switch to update_wiki_page, not to retry.
  • update_wiki_page is a PATCH: omit content to keep the current content. Passing title RENAMES the page and breaks every existing link to the old name — update those links in the same pass.
  • content is plain Markdown — the tools handle the API's base64 encoding for you; never send base64 yourself.
  • Special pages: Home (the landing page), _Sidebar (persistent navigation), _Footer (page footer). They are ordinary pages to write, but their titles are reserved.
  • History: list_wiki_revisions({ pageName }) shows who changed what; use it before reverting or when summarizing changes. Deleting a page is only recoverable from the wiki git clone — there is no skill for deletion; require explicit user confirmation.

Read the full file on GitHub · 36 lines

Files

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.

Changes

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.

  1. 2d ago First seen · 36 lines · 89 tokens per session scan A 0fb9c33b7440

Subscribe to this mod's changes

gitea-write-wiki is a skill published in the GitHub repository amonstack/gitea_mcp (1 stars, last pushed 9d ago), licensed MIT. It adds 89 tokens to every session and 866 once invoked, about $0.0004 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.

Git and workflowWriting and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens