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 saeedkolivand/ai-job-hunter-app --skill docs-standardsgit clone --depth 1 https://github.com/saeedkolivand/ai-job-hunter-appWrote 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/saeedkolivand/ai-job-hunter-app/docs-standards)<a href="https://agentmods.dev/skills/saeedkolivand/ai-job-hunter-app/docs-standards"><img src="https://agentmods.dev/badge/skills/saeedkolivand/ai-job-hunter-app/docs-standards/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/saeedkolivand/ai-job-hunter-app/docs-standards"><img src="https://agentmods.dev/badge/skills/saeedkolivand/ai-job-hunter-app/docs-standards.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.00056 | $0.01018 |
| Opus 5.5 | $0.00022 | $0.00407 |
| Sonnet 5.5 | $0.00011 | $0.00204 |
| Haiku 4.5 | $0.00006 | $0.00102 |
Grade A, and why
docs-standards 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 1mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs standards (project-steward)
Code → docs map
- IPC contract change (
packages/shared/src/ipc/contracts/) → write the prose as TSDoc on the contract member, thenpnpm gen:api.docs/API.mdis generated (scripts/gen-api-docs.mjs) and must never be hand-edited; CI enforces freshness viapnpm gen:api:check. - New domain/module or boundary change →
docs/knowledge/+docs/ARCHITECTURE.md. - Export/template change →
docs/EXPORT_TEMPLATES.md+docs/knowledge/resume-domain.md. - Scraping/provider change →
docs/knowledge/automation-domain.md. - Design-system change →
docs/DESIGN_SYSTEM.md. - Architecture / module / IPC-contract / registry change → also refresh the landing diagrams
apps/landing/src/data/architecture-map.ts+apps/landing/src/content/how-it-works/body.html, then runpnpm check:landing-drift(CI enforces it via the Lint & Format job). - A durable architecture decision → an ADR in
docs/knowledge/decision-records/.
No-drift rule (thin pointers)
Applies to everything under docs/.
Describe shape and contracts; never copy drift-prone literals (scoring weights, thresholds, template/board/applier counts, function signatures, enum members, file lists). Point at the owning source symbol instead (weights → commands/match_resume.rs; templates → export/templates/mod.rs; registries → scraping/boards/mod.rs (SCRAPERS)).
Files in docs/knowledge/ are capped at ~150 lines.
Self-check before saving a doc edit: for every number, name or signature on the page, ask "if someone changed this in the code tomorrow, would this page silently become a lie?" If yes, replace it with a pointer to where it lives.
Generated pages are exempt because they are not editable at all. A file opening with a GENERATED FILE banner (docs/API.md) is rendered from its source by a script; restating the contract is its whole purpose. Fix the TSDoc on the contract member and re-run the generator — never the page.
After editing code or docs
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.
- 1mo ago Changed d8b9bb8919af
- 1mo ago First seen · 56 lines · 56 tokens per session scan A f8af0857a971
docs-standards is a skill published in the GitHub repository saeedkolivand/ai-job-hunter-app (62 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,018 once invoked, about $0.0002 per session on Opus 5.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
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history, or import a local recording. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.
wayfinder
Plan large multi-session initiatives wrapped in fog as a map of linked decision tickets, resolving them sequentially without context degradation.
resume-builder
Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON…
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
sdlc
Route a task to the next synced SDLC workflow based on current artifacts and repo state.
session-report
Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.