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 specsnl/agent-specs --skill autofix-markdown-tablesgit clone --depth 1 https://github.com/specsnl/agent-specsWrote 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/specsnl/agent-specs/autofix-markdown-tables)<a href="https://agentmods.dev/skills/specsnl/agent-specs/autofix-markdown-tables"><img src="https://agentmods.dev/badge/skills/specsnl/agent-specs/autofix-markdown-tables.svg" alt="Measured on agentmods" 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.00117 | $0.00524 |
| Opus 5 | $0.00059 | $0.00262 |
| Sonnet 5 | $0.00023 | $0.00105 |
| Haiku 4.5 | $0.00012 | $0.00052 |
Grade A, and why
autofix-markdown-tables 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
Auto-fix Markdown Tables
Automatically detect and fix misaligned markdown tables across all .md files in the project.
Step 1: Run the formatter
Preferred — the project's own task
Specs projects ship a task for this. Check first:
task --list | grep -E 'md:(fix-tables|fixstyle)'
task md:fix-tables # tables only
task md:fixstyle # tables + markdownlint --fix
Use md:fixstyle when the project also lints markdown in CI (a Markdown workflow running
markdownlint-cli2) — aligning tables alone can still leave the linter red.
Fallback — no Taskfile in this project
docker run --rm --volume $(pwd):/app --workdir /app node:24.15.0-bookworm bash -c "shopt -s globstar && npx --yes markdown-table-formatter **/*.md"
This command:
- Mounts the current directory into a Node.js 24 container
- Uses
shopt -s globstarto enable recursive**glob expansion in bash - Runs
markdown-table-formatteron every.mdfile found recursively - Modifies files in-place — no output is written elsewhere
Step 2: Review the changes
After the formatter runs, check what was changed:
git diff --stat
For a detailed view of the actual table changes:
git diff
Verify that only whitespace/padding inside table cells changed — no content, wording, or structure should be altered. If unexpected changes appear, investigate before proceeding.
Step 3: Confirm
If the diff looks correct, the tables are properly aligned and the files are ready to commit. No further action is needed.
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 Changed · +1 lines dcc35acac251
- 7d ago First seen · 67 lines · 117 tokens per session scan A f2710e43a706
autofix-markdown-tables is a skill published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 3d ago), licensed MIT. It adds 117 tokens to every session and 524 once invoked, about $0.0006 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…