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 wecode-ai/Wegent --skill wiki_submitgit clone --depth 1 https://github.com/wecode-ai/WegentWrote 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/wecode-ai/wegent/wiki_submit)<a href="https://agentmods.dev/skills/wecode-ai/wegent/wiki_submit"><img src="https://agentmods.dev/badge/skills/wecode-ai/wegent/wiki_submit/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/wecode-ai/wegent/wiki_submit"><img src="https://agentmods.dev/badge/skills/wecode-ai/wegent/wiki_submit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.02756 |
| Opus 5.5 | $0.00008 | $0.01102 |
| Sonnet 5.5 | $0.00004 | $0.00551 |
| Haiku 4.5 | $0.00002 | $0.00276 |
Grade A, and why
wiki_submit 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 1mo 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
For every coordinated full-rebuild review action, read
REVIEW_CONTRACT.md completely first. It defines the required
handoffs, phase states, outputs, and completion criteria for both Writer and Reviewer.
Wiki Submit Skill
This skill provides a simple command-line tool to submit wiki documentation pages to the Wegent backend.
Page paths
A page is identified by its --path: index, architecture/backend, modules/indexing.
Lowercase, /-separated, no file extension, at most 4 folders deep. Two paths may not
differ only by case — the projection matches them case-insensitively, so they would
collapse into one page.
Keep a path stable across runs. It is what lets an unchanged page keep its place, its links and its search index. Changing it republishes the page as a deletion plus an insertion, so reword titles freely and move paths rarely.
Send a page's complete content every time. There is no patch format; what you send replaces the page.
A section that holds pages needs a substantive page of its own. If you submit
architecture/backend, also submit architecture with an overview of that section;
for architecture/backend/api, submit both architecture and architecture/backend.
This is a publish requirement: complete refuses a version with any ancestor path
that is not a page. Submit overview pages first where practical, and always before
running complete. Write index as the wiki overview.
Create a slash-separated section only when its parent has a meaningful overview and
at least two independent child pages. If one topic is all that is needed, make it one
page (for example domain-concepts) rather than a parent page plus a one-page folder.
Titles name the subject and the reader's purpose; do not use generic titles such as
"Domain concepts part", "Module part", "Part N", or their translated equivalents.
Link to another wiki page by its complete page path without an extension, for example
[Backend](architecture/backend). Do not use ./architecture/backend.md or a URL: wiki
pages are not files served at those locations.
What ships with it
3 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.
- 1mo ago Changed · +7 lines 3dadcca4b9da
- 1mo ago Changed · +13 lines 9af8d01e5b08
- 1mo ago Changed · +17 lines 143663b4238f
- 1mo ago Changed · +56 lines 31782b2600c1
- 1mo ago First seen · 196 lines · 21 tokens per session scan A 041c2077f207
wiki_submit is a skill published in the GitHub repository wecode-ai/Wegent (872 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 2,756 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
skill-creator
A guide for creating or improving an agent skill: a SKILL.md file that gives an AI a repeatable workflow for a specific task. It covers the skill’s name, search keywords, instructions, failure handling, and examples where needed.
github
A writing guide for GitHub issues, pull requests, code reviews, and release notes in Zhin projects. GitHub is a service where teams track bugs, discuss changes, review code, and publish project updates.
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
openapi-expert
OpenAPI/Swagger expert for API specification design, validation, and code generation.
article-writer
Multi-style article creation skill. Supports 5 writing styles (deep analysis, practical guide, story-driven, opinion, news brief), including complete workflow: material collection → outline → content → formatting. Activated when users mention "write article", "write post", "create", or "draft".
skin-creator
Create and apply a two-asset LobsterAI visual skin from the user's style description. Use only when the AI Skin Designer kit supplies the structured skinpack workflow marker; do not use for ordinary theme or image requests.