Borrowing it
Nothing to install: this file belongs to barseghyanartur/fake.py. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/barseghyanartur/fake.py/main/.agents/skills/update-documentation/SKILL.mdgit clone --depth 1 https://github.com/barseghyanartur/fake.pyWrote 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/barseghyanartur/fake.py/update-documentation)<a href="https://agentmods.dev/skills/barseghyanartur/fake.py/update-documentation"><img src="https://agentmods.dev/badge/skills/barseghyanartur/fake.py/update-documentation.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.00039 | $0.02853 |
| Opus 5 | $0.00019 | $0.01426 |
| Sonnet 5 | $0.00008 | $0.00571 |
| Haiku 4.5 | $0.00004 | $0.00285 |
Grade A, and why
update-documentation 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 8d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documentation Skill
Operation mode: Pure agent-based documentation synchronization.
When the user asks to sync-documentation, the agent:
- Scans source code to extract ground truth (public API, provider methods, CLI commands, factory classes)
- Scans all documentation files
- Identifies misalignments between code and docs
- Auto-fixes documentation to match code (reports what was changed)
This is NOT a Python script - the agent performs all analysis and edits directly.
Agent-Based Sync Process
When sync-documentation is invoked:
Step 1: Extract Ground Truth from Code
Scan source code to identify:
- Public API: Exports from
__all__infake.py(lines 76-150) - Provider methods:
@providerdecorated methods inFakerclass (~lines 400-2000) - Helper functions:
create_inner_*functions (~lines 5400-5700) - CLI commands: Subcommands in
CLIclass (~lines 6500-7000) - Factory classes:
DjangoModelFactory,PydanticModelFactory,SQLAlchemyModelFactory,TortoiseModelFactory - Template classes:
StringTemplate,LazyStringTemplate
Step 2: Scan Documentation Files
Read and analyze:
README.rst- Features, installation, quick startCONTRIBUTING.rst- Developer setup, testing, PR processAGENTS.md- Agent workflowdocs/recipes.rst- Provider examples (1,859 lines)docs/cheatsheet.rst- Quick tricksdocs/creating_files.rst- File generation basics, StringTemplate/LazyStringTemplatedocs/creating_images.rst- Image formatsdocs/creating_pdf.rst- PDF generationdocs/creating_docx.rst- DOCX generationdocs/creating_odt.rst- ODT generationdocs/creating_archives.rst- ZIP, TAR, EML archivesdocs/factories.rst- Factory integrationsdocs/customisation.rst- Custom Faker/Factory usagedocs/cli.rst- CLI commands
Step 3: Identify Misalignments
Compare code ground truth against documentation:
| Doc File | Check Against |
|---|---|
README.rst |
Features list vs __all__ + provider methods |
CONTRIBUTING.rst |
Developer prerequisites vs Makefile/pyproject.toml |
docs/recipes.rst |
Provider examples vs actual Faker methods |
docs/cheatsheet.rst |
Tricks vs provider methods |
docs/creating_images.rst |
7 formats (PNG, SVG, BMP, GIF, TIF, PPM, JPG) vs create_inner_* |
docs/creating_pdf.rst |
PDF methods vs actual implementation |
docs/creating_docx.rst |
DOCX methods vs implementation |
docs/creating_odt.rst |
ODT methods vs implementation |
docs/creating_archives.rst |
ZIP, TAR, EML methods vs implementation |
docs/creating_files.rst |
File generation basics, StringTemplate/LazyStringTemplate usage |
docs/factories.rst |
Factory classes in __all__ vs actual implementations |
docs/customisation.rst |
Customization APIs vs Faker/Factory classes |
docs/cli.rst |
CLI commands vs CLI class subcommands |
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.
- 8d ago First seen · 392 lines · 39 tokens per session scan A dcdb8ab166d3
update-documentation is a skill published in the GitHub repository barseghyanartur/fake.py (20 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 2,853 once invoked, about $0.0002 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
testing-unit
Unit testing patterns for isolated business logic tests — AAA pattern, parametrized tests (test.each, @pytest.mark.parametrize), fixture scoping (function/module/session), mocking with MSW/VCR at network level, and test data management with factories (FactoryBoy, faker-js). Use when writing unit tests, setting up…
test-data-management
Strategic test data generation, management, and privacy compliance. Use when creating test data, handling PII, ensuring GDPR/CCPA compliance, or scaling data generation for realistic testing scenarios.
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-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…