Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_Mallnpx agentmods add skills/fabioc-aloha/alex_skill_mall/github-wiki-flatWrote 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/fabioc-aloha/alex_skill_mall/github-wiki-flat)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/github-wiki-flat"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/github-wiki-flat/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/fabioc-aloha/alex_skill_mall/github-wiki-flat"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/github-wiki-flat.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.00024 | $0.00870 |
| Opus 5 | $0.00012 | $0.00435 |
| Sonnet 5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
github-wiki-flat 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 7d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Wiki Is Flat
Category: GitHub Time Saved: 1-2 hours debugging broken links Battle-tested: Yes — wiki publishing automation
The Problem
You organize your wiki source files in a nice folder structure:
wiki/
getting-started/
installation.md
configuration.md
api/
endpoints.md
authentication.md
You push to GitHub Wiki. All your internal links break. Pages appear at root level with mangled names.
Why It Happens
GitHub Wiki has no folder hierarchy. Every page renders at the wiki root. Folders in your source become part of the page name (with dashes).
wiki/getting-started/installation.md
→ renders at: /wiki/getting-started-installation
wiki/api/endpoints.md
→ renders at: /wiki/api-endpoints
The Rules
1. All Pages Render at Root
Source: docs/guide/setup.md
URL: github.com/user/repo/wiki/guide-setup
NOT: github.com/user/repo/wiki/guide/setup ❌
2. Links Must Use Flat Names
<!-- In wiki/getting-started/installation.md -->
<!-- ❌ WRONG — relative path -->
See [configuration](./configuration.md)
<!-- ✅ CORRECT — flat wiki name -->
See [configuration](getting-started-configuration)
<!-- ❌ WRONG — assumes hierarchy -->
See [endpoints](../api/endpoints.md)
<!-- ✅ CORRECT — flat wiki name -->
See [endpoints](api-endpoints)
3. _Sidebar.md Is Ground Truth
The sidebar defines your navigation. All links in _Sidebar.md must use flat names:
<!-- _Sidebar.md -->
**Getting Started**
- [Installation](getting-started-installation)
- [Configuration](getting-started-configuration)
**API Reference**
- [Endpoints](api-endpoints)
- [Authentication](api-authentication)
Link Rewriting Automation
If you maintain wiki source in a folder structure, automate link rewriting on publish:
function rewriteWikiLinks(content, sourceDir) {
// Convert relative paths to flat wiki names
return content.replace(
/\[([^\]]+)\]\(\.?\/?([^)]+)\.md\)/g,
(match, text, path) => {
// ./sibling.md → folder-sibling
// ../other/page.md → other-page
const flatName = path
.replace(/^\.\.?\/?/, '')
.replace(/\//g, '-');
return `[${text}](${flatName})`;
}
);
}
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.
- 7d ago First seen · 146 lines · 24 tokens per session scan A 6ed15a403b0e
github-wiki-flat is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 870 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
review-pr
Perform a comprehensive code review of a pull request.
ship
Comprehensive pre-deployment verification to ensure release readiness.
verify-release
Use when checking whether a Proofpack release candidate has complete local evidence before packaging.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
ai-agents-generation-and-release
Operate the ai-agents generation and release machinery, covering the seven buildall.py generators, generateagents.py, syncpluginlib.py, the drift gates, the version-free plugin manifests, and the npm publish path. Use when you say regenerate the mirrors, run the drift checks, why is the plugin version gate red…
chestertons-fence
Investigate historical context of existing code, patterns, or constraints before proposing changes. Automates git archaeology, PR/ADR search, and dependency analysis to prevent removing structures without understanding their purpose. Use when you ask "why does this code/constraint exist", "is it safe to remove this".…