pchalasani/claude-code-tools is a collection of command-line tools, skills, agents, hooks, plugins, and commands for improving work with Claude Code, Codex-CLI, and similar coding agents. It is used by developers who want reusable productivity features and workflows for terminal-based AI coding assistants. The catalogue entries are components of, or extensions for, these coding-agent workflows.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add pchalasani/claude-code-tools --skill session-searchgit clone --depth 1 https://github.com/pchalasani/claude-code-toolsWrote 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.
[](https://agentmods.dev/skills/pchalasani/claude-code-tools/session-search)<a href="https://agentmods.dev/skills/pchalasani/claude-code-tools/session-search"><img src="https://agentmods.dev/badge/skills/pchalasani/claude-code-tools/session-search/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.
<a href="https://agentmods.dev/skills/pchalasani/claude-code-tools/session-search"><img src="https://agentmods.dev/badge/skills/pchalasani/claude-code-tools/session-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 2 findings, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Supply Chain · line 77 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- low Supply Chain · line 78 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00033 | $0.00657 |
| Opus 5.5 | $0.00013 | $0.00263 |
| Sonnet 5.5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade C, and why
session-search scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -LsSf https://astral.sh/uv/install.sh | sh # uv Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -LsSf https://astral.sh/uv/install.sh | sh # uv Copies of this mod
1 near-identical copy found in the catalogue:
- session-search — 89% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If you are Claude Code: Do NOT use this skill directly. Use the
session-searchersubagent via the Task tool instead - it handles this more efficiently without polluting your context.
session-search
Search and find previous code agent sessions (Claude-Code or Codex-CLI) for specific work, decisions, or code patterns.
Workflow
- Understand the query: Identify what the user is looking for (code patterns, decisions, specific work, design direction)
- Search with aichat: Run
aichat search --json -n 10 "[query]"(use-g "project"to filter by project) - Parse results: Use
jqto extract fields from JSONL output (session_id, project, created, snippet, file_path) - Deep dive if needed: Read session files at
~/.claude/projects/*/[session-id].jsonl(max 3 files) - Summarize: Return a focused summary with key findings and references
Run aichat search --help to see all options (date filters, branch filters, etc.)
and JSONL field names.
Output Format
Return a concise summary containing:
- Key Findings: 2-3 bullet points answering the query
- Relevant Sessions: Session IDs and dates for reference
- Specific Content: Code snippets or quotes if directly relevant
Format as clean markdown, not raw JSON.
Example
Query: "Find sessions where we discussed authentication design"
aichat search --json -n 10 "authentication design"
Summary:
- Session abc123 (Dec 10): Discussed JWT vs session-based auth, decided on JWT
- Session def456 (Dec 8): Implemented refresh token rotation pattern
Constraints
- ALWAYS use
--jsonflag with aichat search (otherwise it spawns interactive UI) - NEVER return raw JSON output to the user - summarize and distill findings
- NEVER read more than 3 session files per query
- If no results found, suggest alternative search terms
- ONLY report information directly observed in files - never infer or extrapolate
Error Handling
If aichat search command fails or is not found, ask user to install:
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 · 80 lines · 33 tokens per session scan C 9c70c233950c
session-search is a skill published in the GitHub repository pchalasani/claude-code-tools (2,031 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 657 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
session-search compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| session-searchpchalasani/claude-code-tools | Skill | 2.0k | yesterday | MIT | C | 33 | Claude Code |
| obsidianlvndry/jazz | Skill | 55 | yesterday | MIT | A | 71 | Claude Code, Codex |
| knowledge-session-state-and-context-active-turn-interactions-and-recoveryechoVic/blade-code | Skill | 181 | 24d ago | MIT | A | 161 | Claude Code, Codex |
| knowledge-session-state-and-context-session-catalog-fork-rewind-and-exportechoVic/blade-code | Skill | 181 | 24d ago | MIT | A | 140 | Claude Code, Codex |
| knowledge-session-state-and-context-compaction-pipeline-and-checkpointsechoVic/blade-code | Skill | 181 | 24d ago | MIT | A | 144 | Claude Code, Codex |
| knowledge-session-state-and-contextechoVic/blade-code | Skill | 181 | 24d ago | MIT | A | 133 | Claude Code, Codex |
| contextepicsagas/epic-harness | Skill | 20 | yesterday | Apache-2.0 | A | 33 | Claude Code |