Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add testdouble/han/plugin install han-coreWrote 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/testdouble/han/project-discovery)<a href="https://agentmods.dev/skills/testdouble/han/project-discovery"><img src="https://agentmods.dev/badge/skills/testdouble/han/project-discovery/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/testdouble/han/project-discovery"><img src="https://agentmods.dev/badge/skills/testdouble/han/project-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00097 | $0.01802 |
| Opus 5.5 | $0.00039 | $0.00721 |
| Sonnet 5.5 | $0.00019 | $0.00360 |
| Haiku 4.5 | $0.00010 | $0.00180 |
Grade A, and why
project-discovery scanned grade A with 0 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
- Default branch: !
git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo unknown - AGENTS.md: !
find . -maxdepth 1 -name "AGENTS.md" -type f - CLAUDE.md: !
find . -maxdepth 1 -name "CLAUDE.md" -type f - README: !
find . -maxdepth 1 -name "README*" -type f - personal config directory: !
bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude" - project .han/config.md: !
cat .han/config.md 2>/dev/null || echo ""
As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read
that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md
probe supplies content, apply it per config-rule.md, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
Project Discovery
This skill discovers the project's core attributes and writes them as a concise ## Project Discovery section
directly into the project's AGENTS.md or CLAUDE.md — not a separate file. The output is small by design: a few notes
on where things live, the languages and frameworks, and the commands to run, so an AI agent working in the repo can find
its way around. It is not an exhaustive inventory.
Step 1: Choose and read the target file
Pick the single file this discovery is written into, by priority:
- If AGENTS.md exists (the label above is non-empty), the target is AGENTS.md.
- Otherwise, if CLAUDE.md exists, the target is CLAUDE.md.
- If neither exists, the target is a new CLAUDE.md at the repository root, which you will create in Step 4.
If the target file already exists, read it in full and build the deduplication baseline: a list of everything the
file already documents that this skill would otherwise write — directory and folder locations, languages, frameworks,
package manager, build/test/lint/dev commands, and the docs, ADR, and coding-standards directories. Note whether the
file already has a ## Project Discovery section.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 133 lines · 97 tokens per session scan A 10d5b00f24f9
project-discovery is a skill published in the GitHub repository testdouble/han (304 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 1,802 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
security-architecture-review
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a…