What is knowhub CLAUDE.md?

Commit-writing instructions for KnowHub, a software project. They require commit messages to follow Angular conventional commits, a format that labels changes such as features, fixes, tests, or documentation.

Use them when creating commits in the KnowHub repository, especially to choose the right change type, scope, wording, and length.

They keep the project's commit history consistent and make each change's purpose easier to identify. The rules also prevent unclear or overly long first lines.

How yujiosaka/knowhub configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to yujiosaka/knowhub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/yujiosaka/knowhub/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/yujiosaka/knowhub

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/yujiosaka/knowhub/claude-md/github.svg)](https://agentmods.dev/instructions/yujiosaka/knowhub/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/yujiosaka/knowhub/claude-md"><img src="https://agentmods.dev/badge/instructions/yujiosaka/knowhub/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/yujiosaka/knowhub/claude-md"><img src="https://agentmods.dev/badge/instructions/yujiosaka/knowhub/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 824 This file is loaded in full into every session.

When invoked 824 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00824	$0.00824
Opus 5.5	$0.00330	$0.00330
Sonnet 5.5	$0.00165	$0.00165
Haiku 4.5	$0.00082	$0.00082

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

Security

Grade A, and why

knowhub CLAUDE.md 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.

CLAUDE.md · 119 lines

How it starts

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

Claude Code Configuration

This document contains instructions for Claude Code to ensure all commits follow Angular commit conventions.

Commit Message Format

IMPORTANT: All commit messages MUST follow the Angular conventional commit format:

type(scope): description

[optional body]

[optional footer(s)]

Required Format Rules

Type: Use lowercase, required
Scope: Use lowercase, optional but recommended
Description:
- Start with lowercase letter
- No period at the end
- Present tense, imperative mood
- Maximum 72 characters for the entire first line

Commit Types

Use these commit types (in order of preference):

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor: A code change that neither fixes a bug nor adds a feature
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
perf: A code change that improves performance
ci: Changes to CI configuration files and scripts
build: Changes that affect the build system or external dependencies
revert: Reverts a previous commit

Scope Guidelines

Common scopes for this project:

cli: Command-line interface changes
core: Core knowhub functionality
config: Configuration-related changes
plugins: Plugin system changes
sync: Synchronization functionality
templates: Template-related changes
docs: Documentation changes
tests: Test-related changes
deps: Dependency updates

Description Guidelines

Use imperative mood: "add feature" not "added feature"
Keep it concise but descriptive
Explain WHAT changed, not HOW
Start with lowercase letter
No period at the end

Examples

Good Commit Messages

feat(cli): add sync command for knowledge files
fix(config): resolve parsing error for nested configurations
docs(readme): update installation instructions
refactor(plugins): simplify plugin registry initialization
test(sync): add integration tests for GitHub plugin
chore(deps): update biome to v1.9.4
style(cli): fix formatting in help command
perf(sync): optimize file processing for large repositories

Read the full file on GitHub · 119 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.

2mo ago First seen · 119 lines · 824 tokens per session scan A 8e9f721d54f0

Subscribe to this mod's changes

knowhub CLAUDE.md is an instructions file published in the GitHub repository yujiosaka/knowhub (41 stars, last pushed 1y ago), licensed MIT. It adds 824 tokens to every session, about $0.0033 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-30.

Commits Git and workflow ai coding-assistant developer-tools

knowhub CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
knowhub CLAUDE.mdyujiosaka/knowhub	Instructions file	41	1y ago	MIT	A	824	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

knowhub: Instructions file for Claude Code