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 fortunto2/solo-factory --skill auditgit clone --depth 1 https://github.com/fortunto2/solo-factoryWrote 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/fortunto2/solo-factory/audit)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/audit"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/audit/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/fortunto2/solo-factory/audit"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/audit.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.00052 | $0.01267 |
| Opus 5 | $0.00026 | $0.00633 |
| Sonnet 5 | $0.00010 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
solo-audit 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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit
Audit the knowledge base for quality issues: missing frontmatter, broken links, tag inconsistencies, orphaned files, and coverage gaps. Works on any markdown-heavy project.
Steps
-
Parse focus area from
$ARGUMENTS(optional). If provided, focus on that area (e.g., "tags", "frontmatter", "links"). If empty, run full audit. -
Find all markdown files: Use Glob to find all .md files, excluding common non-content directories:
.venv/,node_modules/,.git/,archive/,.archive_old/. -
Frontmatter audit: First, scan a sample of existing files (first 10-20) to detect the frontmatter schema in use (which fields exist, what values are common for
typeandstatus). Then for each markdown file, check:- Has YAML frontmatter (starts with
---and has closing---) - Core fields present:
title,tags(and any other fields consistently used across the KB) typeandstatusvalues (if used) are consistent with the detected schematagsis a non-empty list Track files missing frontmatter and files with incomplete/invalid frontmatter.
- Has YAML frontmatter (starts with
-
Link check: Look for broken internal links:
- Grep for markdown links
\[.*\]\(.*\.md\)and verify each target file exists - If a link-checking script exists in the project (e.g.,
scripts/check_links.py), run it as well
- Grep for markdown links
-
Tag consistency audit: Use Grep to find all
tags:sections across .md files. Look for:- Near-duplicate tags (e.g., "ai" vs "AI" vs "artificial-intelligence")
- Tags used only once (potential typos)
- Very common tags that might be too broad List all unique tags with counts.
-
Orphaned files: Check which files are NOT referenced in any other file's
related:field. Files that exist but are never cross-referenced may be orphaned. -
Content quality: Find documents that appear to be ideas or opportunities (based on detected
typefield or directory location) and check:- Documents still in
draftstatus for more than 30 days - Documents missing key metadata fields that other similar documents have
- Documents with very little content (< 100 words, excluding frontmatter)
- Documents still in
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.
- 9d ago First seen · 114 lines · 52 tokens per session scan A 7c1c161fd503
solo-audit is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,267 once invoked, about $0.0003 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-30.
Other skills, from other repositories
typescript-providers
Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, and Claude Agent SDK. Use for provider-specific TS work; do not use for core-only changes.
publication-chart-skill
This skill should be used when the user asks for a publication-quality scientific figure or table, wants help choosing the right chart for results, needs a paper-ready pubfig or pubtab workflow, wants a figure + companion table for a results section, wants an Excel sheet turned into publication-ready LaTeX, or wants…
memstack-business-scope-of-work
Use this skill when the user says 'scope of work', 'SOW', 'define scope', 'project scope', 'write SOW', 'scope document', or is defining project boundaries, deliverables, and acceptance criteria for a formal engagement. Do NOT use for proposals, contracts, or invoicing.
memstack-business-invoice-generator
Use this skill when the user says 'invoice', 'generate invoice', 'create invoice', 'bill client', 'line items', 'payment terms', or needs professional invoices with tax calculations and payment instructions. Do NOT use for contracts or financial projections.
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…
summarize-transcript
Analyze and summarize a transcript, meeting notes, or discussion thread into a clear actionable document.