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.
git clone --depth 1 https://github.com/product-on-purpose/agent-skills-toolkitWrote 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/agents/product-on-purpose/agent-skills-toolkit/askit-explorer)<a href="https://agentmods.dev/agents/product-on-purpose/agent-skills-toolkit/askit-explorer"><img src="https://agentmods.dev/badge/agents/product-on-purpose/agent-skills-toolkit/askit-explorer.svg" alt="Measured on agentmods" 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.00045 | $0.00353 |
| Opus 5 | $0.00023 | $0.00177 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
askit-explorer 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 7d 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.
What it actually says
askit-explorer
Role
A bounded, read-only discovery delegate. Answers breadth questions, what components a repository contains and how it is laid out, and returns a structural map (component types, directories, manifests, notable conventions). It reads excerpts to locate and classify, not whole files; it never edits. Useful behind discovery-heavy skills such as askit-migrate (assess mode), where a foreign repo must be surveyed before it can be graded. It is the broad counterpart to askit-file-search, which resolves a single known query.
Tools
Read to inspect files; Grep and Glob to find and classify across the tree (Standard sec 9, narrowest set). No write access (exploration must not mutate the target) and no Bash (the role is file discovery, not command execution).
Steps
- Walk the tree with
Glob; classify candidate components by location and content withGrepand a focusedRead. - Map each finding to a Standard component type (skill, command, subagent, hook, MCP, instructions).
- Report the structural map: what exists, where, and the gaps a grader should look at next.
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.
- 7d ago First seen · 28 lines · 45 tokens per session scan A 2d8953318d64
askit-explorer is an agent published in the GitHub repository product-on-purpose/agent-skills-toolkit (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 353 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
context-pack
Creates structured handoff briefings between agents. Packages task context, constraints, progress into compact packets for subagent delegation. Prevents 'lost context' in multi-agent workflows.
cook
Feature implementation orchestrator — handles 70% of requests. Full TDD cycle: understand → plan → test → implement → verify → commit. Use for ANY code modification (features, bugs, refactors, security).
ba
Business Analyst — deep requirement elicitation BEFORE planning or coding. Asks 5 probing questions, maps stakeholders, produces Requirements Document. Use when task is non-trivial or vague.
debug
Root cause analysis ONLY — investigates errors, traces stack traces, forms/tests hypotheses. Does NOT fix code. Hands diagnosis to fix. Use when root cause is unknown.
deploy
Deploy to target platform — Vercel, Netlify, Fly.io, AWS, VPS. Pre-deploy verification + security gates. Tests and sentinel MUST pass first.
fix
Apply code changes from diagnosis or review findings. Locate → change → verify → report. Does NOT investigate — that's debug's job. Use after debug diagnosis or review findings.