setup-doc-conventions

setup-doc-conventions is a skill for Claude Code from mayank-io/mstack. It costs 74 tokens per session (720 once invoked), scanned A, original, MIT.

A project setup skill for a documentation system using templates, dashboards, and Obsidian, a note-taking application.

In plain words
What is it for?
It is for creating documentation templates and dashboards, configuring Obsidian, and adding documentation guidance to CLAUDE.md.
Why use it?
It removes the repetitive work of creating a consistent documentation folder and connecting it to project instructions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Part of the dev plugin — 12 skills shipped together

Good fit It is for creating documentation templates and dashboards, configuring Obsidian, and adding documentation guidance to CLAUDE.md.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mayank-io/mstack/setup-doc-conventions
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 mayank-io/mstack --skill setup-doc-conventions
Clone the repo
git clone --depth 1 https://github.com/mayank-io/mstack

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 12 skills.

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 setup-doc-conventions

README.md
[![agentmods](https://agentmods.dev/badge/skills/mayank-io/mstack/setup-doc-conventions/github.svg)](https://agentmods.dev/skills/mayank-io/mstack/setup-doc-conventions)
Your own site
<a href="https://agentmods.dev/skills/mayank-io/mstack/setup-doc-conventions"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/setup-doc-conventions/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.

agentmods 80×15 button for setup-doc-conventions

Your own site · 80×15
<a href="https://agentmods.dev/skills/mayank-io/mstack/setup-doc-conventions"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/setup-doc-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 720 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.
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.00074 $0.00720
Opus 5.5 $0.00030 $0.00288
Sonnet 5.5 $0.00015 $0.00144
Haiku 4.5 $0.00007 $0.00072

Measured 2mo ago against content hash 4079dfa78c50, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-doc-conventions 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 2mo 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.

plugins/dev/skills/setup-doc-conventions/SKILL.md · 78 lines

How it starts

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

Set up the doc-conventions system in this project. Follow these steps exactly:

1. Create directory structure

mkdir -p docs/templates

2. Copy templates

Copy all 10 doc type templates and dashboard.base from the dev plugin cache into docs/templates/:

  • design.md, impl-plan.md, cutover-plan.md, analysis.md, report.md, postmortem.md, kb.md, ops-guide.md, playbook.md, experiment.md
  • dashboard.base (Obsidian Bases views definition — stays in templates/)

Then copy dashboard.md into docs/dashboard.md (the entry point that transcludes named views from templates/dashboard.base).

Find the plugin cache at: ~/.claude/plugins/cache/mstack/dev/*/templates/

PLUGIN_DIR=$(ls -d ~/.claude/plugins/cache/mstack/dev/*/templates/ 2>/dev/null | head -1)
if [[ -n "$PLUGIN_DIR" ]]; then
  cp "$PLUGIN_DIR"/{design,impl-plan,experiment,cutover-plan,analysis,report,postmortem,kb,ops-guide,playbook}.md docs/templates/
  cp "$PLUGIN_DIR/dashboard.base" docs/templates/dashboard.base
  cp "$PLUGIN_DIR/dashboard.md" docs/dashboard.md
else
  echo "Plugin cache not found. Copy templates manually."
fi

3. Configure Obsidian

If docs/.obsidian/ exists, update docs/.obsidian/app.json to include:

{
  "templateFolder": "templates"
}

If docs/.obsidian/ doesn't exist, create it:

mkdir -p docs/.obsidian
echo '{"templateFolder": "templates"}' > docs/.obsidian/app.json

Ensure the Templates core plugin is enabled in docs/.obsidian/core-plugins.json.

4. Update CLAUDE.md

Read the workflow section template from:

TMPL_DIR=$(ls -d ~/.claude/plugins/cache/mstack/dev/*/templates/ 2>/dev/null | head -1)

Append the contents of $TMPL_DIR/claude-md-workflow-section.md to the project's CLAUDE.md.

If CLAUDE.md doesn't exist, create it with just the workflow section.

5. Commit

git add docs/ CLAUDE.md
git commit -m "feat: set up doc-conventions (templates, dashboard, workflow)"

6. Verify

  • Run ls docs/templates/ — should show 10 template files + dashboard.base
  • Run cat docs/dashboard.md — should show Obsidian transclusion links to dashboard.base views
  • Run cat docs/templates/dashboard.base — should show Obsidian Bases view definitions
  • Open docs/ in Obsidian — dashboard.md should render with tabbed views, templates should be available

Read the full file on GitHub · 78 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. 2mo ago First seen · 78 lines · 74 tokens per session scan A 4079dfa78c50

Subscribe to this mod's changes

setup-doc-conventions is a skill published in the GitHub repository mayank-io/mstack (6 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 720 once invoked, about $0.0003 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-08-31.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens