ctx-agent
Load full context packet. Use at session start or when context seems stale or incomplete.
Best use case
ctx-agent is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Load full context packet. Use at session start or when context seems stale or incomplete.
Teams using ctx-agent should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-agent/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-agent Compares
| Feature / Agent | ctx-agent | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Load full context packet. Use at session start or when context seems stale or incomplete.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Load the full context packet for AI consumption. ## When to Use - At the start of a session to load all context - When context seems stale or incomplete - When switching between different areas of work ## When NOT to Use - The PreToolUse hook already runs `ctx agent` automatically with a cooldown: you rarely need to invoke this manually - Don't run it just to "refresh" if you already have the context loaded in this session ## After Loading **Read the files listed in "Read These Files (in order)"**: the packet is a summary, not a substitute. In particular, read CONVENTIONS.md before writing any code. Confirm to the user: "I have read the required context files and I'm following project conventions." Read and confirm before beginning implementation. ## Flags | Flag | Default | Description | |--------------|---------|---------------------------------------------------| | `--budget` | 8000 | Token budget for context packet | | `--format` | md | Output format: `md` or `json` | | `--cooldown` | 10m | Suppress repeated output within this duration | | `--session` | (none) | Session ID for cooldown isolation (e.g., `$PPID`) | ## Execution ```bash ctx agent $ARGUMENTS ``` **Example: default load:** ```bash ctx agent ``` **Example: smaller packet for limited contexts:** ```bash ctx agent --budget 4000 ``` **Example: with cooldown (how the PreToolUse hook invokes it):** ```bash ctx agent --budget 4000 --session $PPID ``` **Example: JSON for programmatic use:** ```bash ctx agent --format json --budget 8000 ```
Related Skills
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.