skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
levnikolaevich/claude-code-skills157 installs

ln-014-agent-instructions-manager

Creates AGENTS.md canonical and CLAUDE.md @AGENTS.md stub; audits token budget, cache safety, import-pattern compliance. Use when instruction files need alignment.

How do I install this agent skill?

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-014-agent-instructions-manager
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a management tool for agent instruction files (AGENTS.md and CLAUDE.md). It performs audits on token usage, prompt caching efficiency, and configuration consistency. While it accesses and modifies local configuration and project metadata, its actions are transparent and aligned with its stated purpose of maintaining agent environments.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Paths: All file refs relative to skills repo root.

Agent Instructions Manager

Type: L3 Worker Category: 0XX Shared

Creates missing instruction files and audits them (AGENTS.md, CLAUDE.md) for quality, consistency, and best practices. AGENTS.md is the single canonical source of content; CLAUDE.md is a thin @AGENTS.md import stub with bounded harness-specific deltas. This skill is the single owner of instruction-file creation and MCP Tool Preferences insertion or replacement.

MANDATORY READ: Load references/coordinator_summary_contract.md, references/environment_worker_runtime_contract.md, and references/worker_runtime_contract.md MANDATORY READ: Load references/mcp_tool_preferences.md MANDATORY READ: Load references/agent_instructions_writing_guide.md — canonical rationale for the @AGENTS.md import pattern, size budgets, and anti-patterns. All audit checks below trace back to this guide.

Input / Output

DirectionContent
Inputproject context, dry_run flag, optional runId, optional summaryArtifactPath
OutputStructured summary envelope with payload.status = completed / skipped / error, plus created files, audit findings, and warnings in changes / detail

If summaryArtifactPath is provided, write the same summary JSON there. If not provided, return the summary inline and remain fully standalone. If runId is not provided, generate a standalone run_id before emitting the summary envelope.

Runtime

Runtime family: environment-worker-runtime

Phase profile:

  1. PHASE_0_CONFIG
  2. PHASE_1_DISCOVER_FILES
  3. PHASE_2_CREATE_MISSING_FILES
  4. PHASE_3_TOKEN_BUDGET_AUDIT
  5. PHASE_4_PROMPT_CACHE_SAFETY
  6. PHASE_5_CONTENT_QUALITY
  7. PHASE_6_IMPORT_PATTERN_COMPLIANCE
  8. PHASE_7_WRITE_SUMMARY
  9. PHASE_8_SELF_CHECK

Runtime rules:

  • emit summary_kind=env-instructions
  • standalone runs generate their own run_id and write the default worker-family artifact path
  • managed runs require both runId and summaryArtifactPath and must write the summary to the exact provided path
  • always write the validated summary artifact before terminal outcome

Output Contract

Always build a structured env-instructions summary envelope per:

  • references/coordinator_summary_contract.md
  • references/environment_worker_runtime_contract.md

Payload fields:

  • files_found
  • files_created
  • quality_findings
  • token_budget
  • prompt_cache_safety
  • import_pattern_status
  • status

When to Use

  • After editing any instruction file
  • After adding/removing MCP servers or hooks
  • Before release or publishing
  • When sessions degrade (context bloat symptoms)
  • First-time project setup (instruction files missing)

Phase 1: Discover Files

Locate instruction files in target project:

AgentPrimaryCanonical sourceFallback
Claude CodeCLAUDE.mdimports AGENTS.md via @AGENTS.md.claude/settings.local.json
Codex / Cursor / Amp / FactoryAGENTS.mdcanonical.codex/instructions.md

Report: which files exist (found / missing), which harnesses share AGENTS.md directly vs via import.

Phase 1b: Plugin Conflict Check

Skip condition: No enabledPlugins in settings OR all plugins are @levnikolaevich-skills-marketplace.

  1. Read ~/.claude/settings.json → parse enabledPlugins
  2. Filter: enabled=true AND publisher ≠ levnikolaevich-skills-marketplace
  3. For each external plugin:
    • Resolve active install first: matching plugin or marketplace under ~/.claude/plugins/marketplaces/*
    • Read active plugins/*/skills/*/SKILL.md descriptions from that install surface
    • Only if no active install is available, fall back to the latest cache snapshot under ~/.claude/plugins/cache/{publisher}/{plugin}/*/skills/*/SKILL.md
    • Treat cache as forensic fallback only. Never count multiple cache snapshots as separate active conflicts.
    • Match against conflict signal keywords:
SignalKeywords in descriptionOverlap with
Orchestration"orchestrat", "pipeline", "end-to-end", "lifecycle"ln-1000 pipeline
Planning"plan.*implement", "brainstorm", "design.*spec"ln-300 task coordinator
Execution"execut.*plan", "subagent.*task", "task-by-task"ln-400/ln-401 executors
Code review"code.review.*dispatch", "review.*quality.*spec"ln-402/ln-310
Quality gate"quality.*gate", "verification.*complet", "test-driven.*always"ln-500 quality gate
Debugging"systematic.*debug", "root.*cause.*phase"problem_solving.md
Git isolation"worktree.*creat", "git.*isolat"git_worktree_fallback.md
  • Check for hooks/session-start directory in the active install surface first
  1. Score: 2+ signal categories → CONFLICT. 1 → WARN. 0 → safe
  2. CONFLICT: "CONFLICT: {plugin} overlaps with ln-* pipeline ({signals}). Disable?" → AskUserQuestion → if yes, set to false in settings.json
  3. WARN: report, continue

Phase 2: Create Missing Files

Skip condition: All files exist OR dry_run == true (report what would be created).

Canonical model: AGENTS.md is the single source of content. CLAUDE.md is an @AGENTS.md import stub with bounded harness-specific deltas. Create in this order so the stub references a file that already exists.

Step 2a: Detect Project Context

FieldSourceFallback
PROJECT_NAMEpackage.json → namebasename(cwd)
PROJECT_DESCRIPTIONpackage.json → description[TBD: Project description]
DATEcurrent date (YYYY-MM-DD)—
ENABLE_WORKFLOW_PRINCIPLESCaller input (default false)—

Step 2b: Create AGENTS.md (if missing) — canonical

  1. MANDATORY READ: Load plugins/documentation-pipeline/skills/ln-111-root-docs-creator/references/templates/agents_md_template.md
  2. Replace {{PROJECT_NAME}}, {{PROJECT_DESCRIPTION}}, {{DATE}}, and {{DEV_COMMANDS_*}} placeholders
  3. If ENABLE_WORKFLOW_PRINCIPLES=true: replace {{WORKFLOW_PRINCIPLES_BLOCK}} with the full content of plugins/documentation-pipeline/skills/ln-111-root-docs-creator/references/templates/agents_md_workflow_principles.md. Otherwise strip the placeholder line and its leading HTML comment.
  4. Mark remaining {{...}} as [TBD: placeholder_name]
  5. Write to target project root

Step 2c: Create CLAUDE.md (if missing) — import stub

  1. MANDATORY READ: Load plugins/documentation-pipeline/skills/ln-111-root-docs-creator/references/templates/claude_md_template.md
  2. Replace {{PROJECT_NAME}} only
  3. Write to target project root
  4. Verify the file contains exactly one @AGENTS.md line and is ≤50 lines total
  5. Do NOT copy any content from AGENTS.md into CLAUDE.md — the @ import handles it at session load time

Step 2e: Report Creations

List each created file with its source (template agents_md_template.md, template claude_md_template.md stub).

Phase 3: Token Budget Audit

Line-count budgets align with the Anthropic official target (<200 lines per CLAUDE.md file) and the IFScale instruction-ceiling research. See references/agent_instructions_writing_guide.md for the full rationale.

CheckPassWarnFail
AGENTS.md line count≤150151-200>200
CLAUDE.md line count (stub)≤2021-50>50
User-added imperative count in AGENTS.md≤100101-150>150

Imperative counter: lines matching ^\s*- inside rule sections, plus any line containing MUST\|NEVER\|ALWAYS\|DO NOT. Cite the IFScale benchmark (arxiv 2507.11538) in WARN / FAIL messages.

Report table per file with line count and imperative count (for AGENTS.md).

Phase 4: Prompt Cache Safety

Check each file for content that breaks prefix-based prompt caching:

#CheckPatternSeverity
1No timestampsgrep -E '\d{4}-\d{2}-\d{2}.\d{2}:\d{2}'WARN
2No dates in content`grep -E '(JanuaryFebruary
3No dynamic countsgrep -E '\d+ skills|\d+ tools|\d+ servers' (hardcoded counts change)WARN
4No absolute paths`grep -E '[A-Z]:\/home/
5Stable structureNo conditional sections (if X then include Y)INFO

Phase 5: Content Quality

#CheckPassFail
1Has build/test commandsFound npm|cargo|pytest|dotnet commands in AGENTS.mdMissing — add essential commands
2No abstract principlesNo "write quality code", "follow best practices"Found vague instructions
3No redundant docsNo API docs, no full architecture descriptionFound content discoverable from code
4Has hard boundariesFound NEVER|ALWAYS|MUST|DO NOT rules in AGENTS.mdMissing explicit prohibitions
5Compact Instructions section## Compact Instructions present in AGENTS.md with preservation prioritiesMissing — sessions lose decisions on /compact
6MCP Tool PreferencesCanonical policy section in AGENTS.md matches references/mcp_tool_preferences.mdMissing or outdated — agents use suboptimal tools
7No tool output examplesNo large code blocks or command outputsFound — bloats every turn

Checks #1–#6 evaluate AGENTS.md only because CLAUDE.md inherits that content via the @AGENTS.md import. Checks on the delta itself live in Phase 6.

Phase 5b: Auto-fix Fixable Issues

For each FAIL in Phase 5, attempt auto-fix before reporting:

Before any auto-fix insertion:

  1. Verify insertion point exists (exact heading found at specific line)
  2. If ambiguous (heading not found) — WARN and skip (report as manual fix needed)
  3. After insertion — verify no duplicate ## Compact Instructions or ## MCP Tool Preferences sections exist in the file
#IssueFixSkip when
5Missing Compact InstructionsInsert ## Compact Instructions section before ## Navigation in AGENTS.mddry_run: true
6Missing or outdated MCP Tool PreferencesInsert or replace section in AGENTS.md from references/mcp_tool_preferences.mddry_run: true
1Missing build/test commandsWARN only (project-specific, cannot auto-generate)--
2Abstract principles foundWARN only (requires human judgment)--

Compact Instructions template (insert in AGENTS.md before ## Navigation or after last rules section):

## Compact Instructions

Preserve during /compact: [Critical Rules], [MCP Tool Preferences table],
[Navigation table], [language/communication rules], [hard boundaries (NEVER/ALWAYS)].
Drop examples and explanations first.

Because CLAUDE.md @AGENTS.md, the preservation list propagates to Claude Code. The harness-specific terminology (/compact vs context compression) lives in the stub delta.

Phase 6: Import Pattern Compliance

AGENTS.md is the canonical source per DOC_ROLE metadata. CLAUDE.md must be a thin @AGENTS.md import stub with bounded harness-specific deltas.

#CheckPassFail
1CLAUDE.md has @AGENTS.md importExactly one @AGENTS.md line presentMissing or multiple — FAIL
2CLAUDE.md delta boundedTotal file ≤50 lines>50 lines — FAIL with drift report
3No content duplicationNo section or rule from AGENTS.md reappears in CLAUDE.mdDuplicate found — FAIL, name the specific overlapping lines

Drift resolution rule: AGENTS.md is the canonical source. For each inconsistency:

  • (a) If content is missing from AGENTS.md but present in CLAUDE.md → move it to AGENTS.md, then remove from the stub.
  • (b) If CLAUDE.md duplicates AGENTS.md content → replace with a single @AGENTS.md import line.
  • (c) If the stub delta exceeds 50 lines → split genuinely harness-specific content into .claude/rules/*.md; everything else moves to AGENTS.md.

Do not "suggest which file is source of truth" based on content volume — AGENTS.md is always the source.

If .hex-skills/environment_state.json reports agents.codex.discovery_violation=true, emit a WARN that Codex skill discovery is drifted and duplicate skill counts from stale cache must not be used as evidence during instruction audits until ln-013-config-syncer repairs the marketplace/plugin alignment.

If .hex-skills/environment_state.json reports agents.codex.permissions_default_ready=false, emit a WARN that Codex CLI startup permissions are drifted from the managed default and instruction audits must not assume full-access startup semantics until ln-013-config-syncer repairs ~/.codex/config.toml.

Phase 7: Report

Agent Instructions Manager:

Created:  (omit section if nothing created)
- AGENTS.md (from template, context from package.json)
- CLAUDE.md (import stub)

Audit:
| File       | Lines | Imperatives | Cache-safe | Quality | Import pattern | Issues |
|------------|-------|-------------|------------|---------|----------------|--------|
| AGENTS.md  | 118   | 47          | OK         | 7/7     | n/a            | OK |
| CLAUDE.md  | 13    | 0           | OK         | 7/7     | OK             | OK |

Import pattern: OK (or N drift issues listed)

Recommendations:
1. Run /init (ln-100) for full context-aware AGENTS.md with project-specific rules

Cross-agent note: Codex CLI 0.120 (2026-04-11) now supports SessionStart hook with /clear vs fresh/resume distinction, matching Claude Code behavior.

Definition of Done

  • All instruction files discovered
  • Missing files created (AGENTS.md from template first; CLAUDE.md as @AGENTS.md import stub second)
  • Token budget within limits: AGENTS.md ≤200 lines, CLAUDE.md ≤50 lines, AGENTS.md imperative count ≤150
  • No prompt cache breakers found (or reported as WARN)
  • Content quality checks passed on AGENTS.md (or issues reported)
  • Auto-fixable issues resolved in AGENTS.md (Compact Instructions, MCP Tool Preferences) or reported if dry_run
  • Import pattern compliance verified: CLAUDE.md contains exactly one @AGENTS.md line and no duplicated AGENTS.md content
  • Report generated with creation log, drift findings, and actionable recommendations
  • No conflicting external plugins detected (or user confirmed keep)
  • Structured summary returned
  • Summary artifact written to the managed or standalone runtime path

Critical Rule: Non-destructive file edits. Auto-fix inserts sections at verified positions only. Never rewrite the entire instruction file. Preserve all existing content outside the inserted section.

Version: 2.2.0 Last Updated: 2026-03-25

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/levnikolaevich/claude-code-skills/ln-014-agent-instructions-manager">View ln-014-agent-instructions-manager on skillZs</a>