project-docs

project-docs is a skill for Claude Code, Codex from AsyrafHussin/agent-skills. It costs 115 tokens per session (2,637 once invoked), scanned A, original, MIT.

A documentation workflow for PHP, Laravel, Node, TypeScript, and React projects that covers creating, reviewing, organizing, and cleaning up project documents.

In plain words
What is it for?
It is for bootstrapping a docs folder, auditing Markdown files, identifying documentation gaps, setting naming and folder conventions, and maintaining project documentation.
Why use it?
It helps teams find missing or outdated documentation and keep generated or obsolete files from accumulating.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

not rated 72repo 11d ago A scan Socket: passSnyk: passSkillSpector: pass 115 tokens original MIT

Good fit It is for bootstrapping a docs folder, auditing Markdown files, identifying documentation gaps, setting naming and folder conventions, and maintaining project documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asyrafhussin/agent-skills/project-docs
Install

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.

Any agent
npx skills add AsyrafHussin/agent-skills --skill project-docs
Clone the repo
git clone --depth 1 https://github.com/AsyrafHussin/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for project-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/project-docs.svg)](https://agentmods.dev/skills/asyrafhussin/agent-skills/project-docs)
Your own site
<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/project-docs"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/project-docs.svg" alt="Measured on agentmods" height="20"></a>
Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,637 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 20 May 2026
  • Snyk pass 20 May 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00115 $0.02637
Opus 5 $0.00057 $0.01319
Sonnet 5 $0.00023 $0.00527
Haiku 4.5 $0.00012 $0.00264

Measured 8d ago against content hash 1c405f53a623, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

project-docs 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.

skills/project-docs/SKILL.md · 246 lines

How it starts

The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Documentation

End-to-end documentation lifecycle for PHP/Laravel and Node/TypeScript/React projects. Contains 25 rules across 6 categories covering folder structure, naming conventions, essential files, content quality (including AI-slop detection), cleanup of accumulated junk, and lifecycle. Supports bootstrap mode (set up docs in a new project), audit mode (find what's missing, stale, bloated, or junk), and reference mode (conventions lookup).

Metadata

  • Version: 1.0.0
  • Scope: PHP / Laravel + Node / TypeScript / React projects
  • Rule Count: 25 rules across 6 categories
  • License: MIT

How to Use This Skill — Three Modes

Mode 1: Bootstrap (new project / missing docs)

When the user asks "set up docs", "what docs does this project need", or starts a new project — walk through the bootstrap steps:

  1. Detect project type (Laravel? React? Both?) — composer.json, package.json, artisan binary
  2. Inventory existing docs — list every .md file with its location and last-modified date
  3. Identify gaps — compare against the Essential Files checklist; report what's missing
  4. Propose folder structuredocs/ with sub-folders (architecture/, adr/, guides/, runbooks/, archive/) based on project size
  5. Offer to scaffold templates — README, CHANGELOG, LICENSE, CONTRIBUTING, SECURITY, ADR-0001 — generate with user approval, do not auto-create
  6. Suggest CI gates — markdown-lint, broken-link checker (lychee), CHANGELOG-on-PR enforcement

Mode 2: Audit (existing project cleanup)

When the user asks "audit docs", "clean up markdown", or "what should I delete" — produce a classified ledger.

For each .md file in the repo:

  • KEEP — file is essential and current
  • UPDATE — file is essential but stale (e.g., README contradicts current setup)
  • ARCHIVE — superseded but historically useful — move to docs/archive/<year>/
  • DELETE — AI-generated plan files, empty stubs, duplicates, orphaned drafts
  • MOVE — wrong location or wrong name (e.g., MyArchitectureNotes.md at root → docs/architecture/overview.md)

Read the full file on GitHub · 246 lines

Changes

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.

  1. 8d ago First seen · 246 lines · 115 tokens per session scan A 1c405f53a623

Subscribe to this mod's changes

project-docs is a skill published in the GitHub repository AsyrafHussin/agent-skills (72 stars, last pushed 11d ago), licensed MIT. It adds 115 tokens to every session and 2,637 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-30.

Related

Other skills, from other repositories

code-humanizer

Use when AI-written code needs structural cleanup or when implementing a change under a guard against AI coding slop — duplicated reimplementations of existing helpers, try-import fallbacks, broad exception swallowing, speculative abstraction layers, v2 copies, dead "for future use" code, narrating comments …

LeonardNJU/code-humanizer · 100 tokens

slop-review

Read-only slop review of prose, documentation, reports, agent output, commit messages or PR descriptions. Use when someone asks what is wrong with a draft, asks for an editorial or quality review, asks whether text is padded, vague, puffed up, unsourced or hollow, or asks whether writing "sounds like AI". Produces a…

AgriciDaniel/anti-slop · 187 tokens

slop-verify

Verification pass for citations, links, package names and vendor residue. Use when someone asks whether the sources in a document are real, asks to check DOIs, ISBNs, arXiv IDs or URLs, asks whether a cited source actually supports the claim attached to it, asks to check that imported packages exist, or asks to strip…

AgriciDaniel/anti-slop · 171 tokens

anti-slop-brain

Scaffold and operate Anti-Slop Brain, a source-cited Obsidian brain for detection and repair of AI slop in prose, code, documentation, and agent output, grounded in corpus evidence rather than authorship detection. Use when the user says "anti-slop-brain", "Anti-Slop Brain", "create a detection and repair of AI slop…

AgriciDaniel/anti-slop · 152 tokens

slop-code

Slop review and repair for source code, tests, configuration, generated documentation, README files, commit messages and pull request descriptions. Use when someone asks to review generated or agent-written code for quality, asks whether a diff is padded or ceremonial, asks about hallucinated or slopsquatted imports…

AgriciDaniel/anti-slop · 161 tokens

anti-slop

Router for the anti-slop toolkit. Use when someone asks to review, clean, de-slop, humanize, or quality-check prose, documentation, code, commit messages, PR descriptions, or agent output, or asks whether some writing "sounds like AI". Also use for verifying citations, DOIs, links and imported package names, for…

AgriciDaniel/anti-slop · 201 tokens