Audit the health of an AI-coding harness — the CLAUDE.md / AGENTS.md files, rules, skills, agents, hooks, and commands that steer an agent in a repository — across four questions a linter cannot answer: is it TRUE (does it match the real code?), is it USED (do skills actually trigger and does the loop actually verify?), is it AFFORDABLE (is it inside the budget where instructions are still followed?), and is it SAFE (is a live, accurate instruction still a good idea — permission bypasses, unpinned remote scripts, untrusted content flowing in as instructions? — safety findings are flagged for the user's decision, never auto-removed). Then surgically correct or remove only what is proven wrong or dead. Use whenever the steering layer may have rotted or may not be working: "하네스 점검해줘", "하네스 드리프트 감사", "CLAUDE.md가 실제랑 맞는지 봐줘", "룰/스킬이 최신인지 확인해줘", "스킬이 제대로 활용되는지 봐줘", "루프 엔지니어링 잘 되고 있는지 검토해줘", "죽은 훅/커맨드 정리해줘", "하네스 안전한지 점검해줘", "audit my harness", "check the rules still match the real stack", "are my skills actually being used", "review the agent loop", "is my harness safe", after a stack or tooling migration, or when onboarding a repo whose steering docs look stale. Not a codebase security audit — it reads the steering layer, not application code. Every finding must be backed by stated-versus-measured evidence; never guess the correct value, and never remove a live path because it merely looks unused.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategorySecurityStars0
About this skill
Audit the health of an AI-coding harness — the CLAUDE.md / AGENTS.md files, rules, skills, agents, hooks, and commands that steer an agent in a repository — across four questions a linter cannot answer: is it TRUE (does it match the real code?), is it USED (do skills actually trigger and does the loop actually verify?), is it AFFORDABLE (is it inside the budget where instructions are still followed?), and is it SAFE (is a live, accurate instruction still a good idea — permission bypasses, unpinned remote scripts, untrusted content flowing in as instructions? — safety findings are flagged for the user's decision, never auto-removed). Then surgically correct or remove only what is proven wrong or dead. Use whenever the steering layer may have rotted or may not be working: "하네스 점검해줘", "하네스 드리프트 감사", "CLAUDE.md가 실제랑 맞는지 봐줘", "룰/스킬이 최신인지 확인해줘", "스킬이 제대로 활용되는지 봐줘", "루프 엔지니어링 잘 되고 있는지 검토해줘", "죽은 훅/커맨드 정리해줘", "하네스 안전한지 점검해줘", "audit my harness", "check the rules still match the real stack", "are my skills actually being used", "review the agent loop", "is my harness safe", after a stack or tooling migration, or when onboarding a repo whose steering docs look stale. Not a codebase security audit — it reads the steering layer, not application code. Every finding must be backed by stated-versus-measured evidence; never guess the correct value, and never remove a live path because it merely looks unused.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Audit the health of an AI-coding harness — the CLAUDE.md / AGENTS.md files, rules, skills, agents, hooks, and commands that steer an agent in a repository — across four questions a linter cannot answer: is it TRUE (does it match the real code?), is it USED (do skills actually trigger and does the loop actually verify?), is it AFFORDABLE (is it inside the budget where instructions are still followed?), and is it SAFE (is a live, accurate instruction still a good idea — permission bypasses, unpinned remote scripts, untrusted content flowing in as instructions? — safety findings are flagged for the user's decision, never auto-removed). Then surgically correct or remove only what is proven wrong or dead. Use whenever the steering layer may have rotted or may not be working: "하네스 점검해줘", "하네스 드리프트 감사", "CLAUDE.md가 실제랑 맞는지 봐줘", "룰/스킬이 최신인지 확인해줘", "스킬이 제대로 활용되는지 봐줘", "루프 엔지니어링 잘 되고 있는지 검토해줘", "죽은 훅/커맨드 정리해줘", "하네스 안전한지 점검해줘", "audit my harness", "check the rules still match the real stack", "are my skills actually being used", "review the agent loop", "is my harness safe", after a stack or tooling migration, or when onboarding a repo whose steering docs look stale. Not a codebase security audit — it reads the steering layer, not application code. Every finding must be backed by stated-versus-measured evidence; never guess the correct value, and never remove a live path because it merely looks unused.
About this listing
Category
Security
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI