Borrowing it
Nothing to install: this file belongs to derailed-dash/dazbo-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/derailed-dash/dazbo-agent-skills/main/GEMINI.mdgit clone --depth 1 https://github.com/derailed-dash/dazbo-agent-skillsWrote 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/instructions/derailed-dash/dazbo-agent-skills/gemini-md)<a href="https://agentmods.dev/instructions/derailed-dash/dazbo-agent-skills/gemini-md"><img src="https://agentmods.dev/badge/instructions/derailed-dash/dazbo-agent-skills/gemini-md/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/instructions/derailed-dash/dazbo-agent-skills/gemini-md"><img src="https://agentmods.dev/badge/instructions/derailed-dash/dazbo-agent-skills/gemini-md.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.00834 | $0.00834 |
| Opus 5 | $0.00417 | $0.00417 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
dazbo-agent-skills GEMINI.md 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Writing and Best Practices
Consider this guide as additional recommendations on top of your own skills-writing training.
- Naming:
- Consider using verb(ing)+noun.
- Avoid vague descriptions, like "documentation".
- Description:
- Always write in 3rd person.
- Be specific and include key terms.
- Include what the skill does and context/triggers for activation. E.g. "Use when…"
- The model is smart. Don't include stuff the model should already know.
- Progressive disclosure:
- Keep the skill body under 500 lines.
- Split files when the body grows large. E.g. "to do x, read ./thing-x.md and follow its instructions"
- Use Unix-style paths when referencing files to load, for all platforms. (This does not apply to actual code or code snippets.)
- Structure longer mds and reference files with a ToC at the top.
- Numbered lists work well for reliability.
- For complex multi-step workflows, consider validating intermediate steps.
- Provide code snippets/commands for low-freedom tasks.
- Avoid offering too many options for solving a single problem.
- Consider providing pre-made scripts for utilities that will be run frequently, to save the model from having to generate the code.
- This improves consistency, and reduces latency and token usage.
- Add information in the skill as to what output is expected from the script call.
- When using MCP tools, fully-qualify the tool name to help avoid not finding the right tool.
- E.g. Use the BigQuery:bigquery_schema tool to retrieve table schemas.
- E.g. Use the GitHub:create_issue tool to create issues.
- Don't assume all pre-reqs and packages are installed. If packages are required, provide instructions for how to install them.
Patterns
Complex Workflows
Research synthesis workflow
Copy this checklist and track your progress:
```
Research Progress:
- [ ] Step 1: Read all source documents
- [ ] Step 2: Identify key themes
- [ ] Step 3: Cross-reference claims
- [ ] Step 4: Create structured summary
- [ ] Step 5: Verify citations
```
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.
- 10d ago First seen · 113 lines · 834 tokens per session scan A e7e08ff3ee91
dazbo-agent-skills GEMINI.md is an instructions file published in the GitHub repository derailed-dash/dazbo-agent-skills (24 stars, last pushed 3d ago), licensed MIT. It adds 834 tokens to every session, about $0.0042 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.