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 arcasilesgroup/ai-engineering --skill ai-exploregit clone --depth 1 https://github.com/arcasilesgroup/ai-engineeringWrote 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/arcasilesgroup/ai-engineering/ai-explore)<a href="https://agentmods.dev/skills/arcasilesgroup/ai-engineering/ai-explore"><img src="https://agentmods.dev/badge/skills/arcasilesgroup/ai-engineering/ai-explore/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/arcasilesgroup/ai-engineering/ai-explore"><img src="https://agentmods.dev/badge/skills/arcasilesgroup/ai-engineering/ai-explore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00116 | $0.01008 |
| Opus 5.5 | $0.00046 | $0.00403 |
| Sonnet 5.5 | $0.00023 | $0.00202 |
| Haiku 4.5 | $0.00012 | $0.00101 |
Grade A, and why
ai-explore 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 27d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read this repository and answer
What it produces
An answer anchored to real paths. Every claim points at file:line, or it is marked as a
guess.
Steps
-
Match the depth to the question, not to a flag. "Where is X" gets a path and a sentence. "How does this work" gets the flow. "Onboard me" gets a tour, and a tour is longer than five sentences by definition.
-
Match the words to who is asking. Somebody who does not code gets what the thing does and what it costs them when it breaks, with the file paths kept as evidence rather than as the answer; somebody who does gets the path first. Ask which if the question does not say, and never answer a business question with a call graph.
-
Find the real entry point before reading anything else. Working outward from the wrong file produces a confident answer about the wrong subsystem.
-
Follow one real path end to end and say what happens at each hop. Never summarise a flow from file names alone — that is the single most common way this goes wrong, and it reads exactly like a correct answer.
-
When the shape is the answer, draw it. Under 70 columns, and every box is a real file that exists:
settings.json ──> src/chain/mod.ts ──> self-protect ──> exit 2 └────────> loop guard (src/guards/loop.ts)
6. Explain what is here, not the pattern in general. If a textbook name applies, one clause
is enough; the reader came for this codebase.
7. Name the pitfall by pointing at a line in this repository. A generic warning helps
nobody; "this returns None on line 84 and the caller does not check" does.
8. If the answer is "it does not exist here", say that in the first sentence.
## Done when
- Every claim has a path, or is explicitly marked as unverified.
- The person could reach your conclusion by opening the files you named, in that order.
- Nothing was changed. This skill reads; it never writes.
## What this is not
Not a design review, not a refactor, and not an opinion about quality. If you spot
something genuinely dangerous, say it in one line at the end and move on.
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.
- 27d ago Changed 0605508a5ced
- 1mo ago Changed ee2df223ed21
- 1mo ago Changed · +30 lines · +1 tokens per session da487c8b9a18
- 1mo ago First seen · 62 lines · 115 tokens per session scan A ea27717b2495
ai-explore is a skill published in the GitHub repository arcasilesgroup/ai-engineering (61 stars, last pushed 5d ago), licensed Apache-2.0. It adds 116 tokens to every session and 1,008 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
322-frameworks-spring-boot-testing-integration-tests
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code…
314-frameworks-spring-kafka
Use when you need to design or implement Kafka messaging in Spring Boot — including topic design, producer/consumer implementation, JSON serialization with Boot factory customizers, Testcontainers @ServiceConnection integration tests, retries and dead-letter topics, idempotency, and error handling. This should trigger…
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
vibeflow-stats
Compiles statistics from audit reports: PASS/PARTIAL/FAIL rates, most violated patterns, most failing DoD checks, and quality trends. Use after running several audits to spot improvement areas.
apex-azure-deploy
WORKFLOW SKILL — Execute Azure deployments (azd up, azd deploy, terraform apply) for already-prepared apps with built-in error recovery. WHEN: 'run azd up', 'run azd deploy', 'push to production', 'go live', 'bicep deploy', 'terraform apply', 'publish to Azure'. DO NOT USE FOR: creating new apps (apex-azure-prepare)…