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 Cribl-Community/claude-cribl-app-plugins --skill app-questionsgit clone --depth 1 https://github.com/Cribl-Community/claude-cribl-app-pluginsWrote 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/cribl-community/claude-cribl-app-plugins/app-questions)<a href="https://agentmods.dev/skills/cribl-community/claude-cribl-app-plugins/app-questions"><img src="https://agentmods.dev/badge/skills/cribl-community/claude-cribl-app-plugins/app-questions/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/cribl-community/claude-cribl-app-plugins/app-questions"><img src="https://agentmods.dev/badge/skills/cribl-community/claude-cribl-app-plugins/app-questions.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.00039 | $0.03798 |
| Opus 5 | $0.00019 | $0.01899 |
| Sonnet 5 | $0.00008 | $0.00760 |
| Haiku 4.5 | $0.00004 | $0.00380 |
Grade A, and why
app-questions 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 12d 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 — 465 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-flight Check
Before proceeding, verify you are in a scaffolded Cribl app folder. If you are not, stop and tell the user: "You must run this skill from within a scaffolded Cribl app folder."
Trigger: Run this skill inside a Cribl app project directory.
Input:
- First run: Answer questions about the app's purpose, workflows, and problems it solves
- Subsequent runs: Choose menu options to view/edit/add/delete definition sections
Output:
- First run: An app definition capturing all answers (
APP_DEFINITION.md) - Subsequent runs: Updated
APP_DEFINITION.mdwith your changes
How to Use
First Run (Creation Mode)
- Scaffold an app in Cribl (Apps > Create App)
- Copy the starter code to your local machine
cdinto the app directory- Run this skill:
/app-questions - Describe what your app does (be specific about the problem and who uses it)
- Answer clarifying questions if needed to sharpen the description
- Answer the full questionnaire about your app
- Review and edit the generated app definition
💡 Tip: Provide specifics in your initial description. Instead of "monitoring tool", say "help our platform team track when customer data pipelines fall behind their SLAs".
Subsequent Runs (Edit Mode)
- Run
/app-questions(the skill detectsAPP_DEFINITION.mdexists) - A menu appears with options to edit parts of the definition
- Choose what to update:
- View/edit the problem statement
- Manage workflows (add/edit/delete)
- Update data & integration points
- Modify permissions & access rules
- Change scope items
- Update UI preferences
- Make your changes interactively
- Review the updated definition
- Exit when done
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.
- 12d ago First seen · 465 lines · 39 tokens per session scan A 85cde3429f41
app-questions is a skill published in the GitHub repository Cribl-Community/claude-cribl-app-plugins (3 stars, last pushed 12d ago), licensed Apache-2.0. It adds 39 tokens to every session and 3,798 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…