AgentStack
SKILL verified MIT Self-run

Codex

skill-knitli-toolshed-codex · by knitli

A Claude skill from knitli/toolshed.

No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-knitli-toolshed-codex

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Codex? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Context Hygiene Skill

name

context-hygiene

description

Audit and maintain AI context files across tool ecosystems. Detects stale claims, contradictions between CLAUDE.md/AGENTS.md/Serena/Cursor/etc., and validates references against the actual codebase.

instructions

When activated, perform a context hygiene audit on the current repository:

1. Discovery

Scan for AI context files across all known tool ecosystems: CLAUDE.md, AGENTS.md, GEMINI.md, .claude/, .gemini/, .codex/, .cursor/, .serena/, .specify/, .roo/, .continue/, claudedocs/, specs/, plans/, docs/, info/, .mcp.json, .cursorrules, .windsurfrules, .continuerules, .clinerules, .aider.conf.yml

Report what you find as an inventory grouped by tool.

2. Staleness check

For each memory/instruction file, extract factual claims (paths, versions, symbols, counts, commands, dependencies) and validate them against the actual codebase. Report what's valid, what's stale, what's broken.

3. Drift detection

Compare memory files against each other to find contradictions and gaps. Flag where different tools have divergent views of the same project.

4. Summary

Produce a prioritized list of issues to fix, with specific file paths, line numbers, and recommended corrections.

After code changes

When you make significant changes to file structure, dependencies, versions, or architecture, proactively check whether any context files need updating. The most important files to keep current are the root-level memory files (CLAUDE.md, AGENTS.md).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.