agentmods.dev

hardware-probe: Instructions file for Gemini CLI

GEMINI.md

hardware-probe GEMINI.md is an instructions file for Gemini CLI from yamaru-eu/hardware-probe. It costs 537 tokens per session, scanned A, original, Apache-2.0.

Project instructions for Yamaru Hardware Probe, a tool that collects hardware information through MCP, a standard way for software agents to use external tools. They cover security, releases, branches, and package size.

In plain words
What is it for?
Use them when editing the probe, its documentation, release notes, package contents, configuration, or publishing workflow.
Why use it?
They help keep hardware identifiers and secrets out of public code while maintaining consistent releases and a small package.

Instructions file for Gemini CLI

Written for Gemini CLI: the file is GEMINI.md.

This is yamaru-eu/hardware-probe's own configuration. It tells Gemini CLI how to work on hardware-probe itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hardware-probe configures →

not rated 7repo 3mo ago A scan 537 tokens original Apache-2.0
View source ↗ yamaru-eu/hardware-probe yamaru.eu
Reuse

Borrowing it

Nothing to install: this file belongs to yamaru-eu/hardware-probe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/yamaru-eu/hardware-probe/main/GEMINI.md
Clone the repo
git clone --depth 1 https://github.com/yamaru-eu/hardware-probe

Made for: Gemini CLI.

Wrote 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.

agentmods badge for hardware-probe GEMINI.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yamaru-eu/hardware-probe/gemini-md/github.svg)](https://agentmods.dev/instructions/yamaru-eu/hardware-probe/gemini-md)
Your own site
<a href="https://agentmods.dev/instructions/yamaru-eu/hardware-probe/gemini-md"><img src="https://agentmods.dev/badge/instructions/yamaru-eu/hardware-probe/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.

agentmods 80×15 button for hardware-probe GEMINI.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/yamaru-eu/hardware-probe/gemini-md"><img src="https://agentmods.dev/badge/instructions/yamaru-eu/hardware-probe/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 537 This file is loaded in full into every session.
When invoked 537 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00537 $0.00537
Opus 5.5 $0.00215 $0.00215
Sonnet 5.5 $0.00107 $0.00107
Haiku 4.5 $0.00054 $0.00054

Measured 1mo ago against content hash 797fb8d30622, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hardware-probe 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 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.

GEMINI.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Yamaru Hardware Probe (MCP)

Guidelines

  1. Language: All documentation (README) and code comments MUST be in English for public distribution.
  2. Distribution: Published on GitHub Packages and npmjs as @yamaru-eu/hardware-probe.
  3. Synchronization: Automated "Squash & Sync" workflow to yamaru-eu/hardware-probe.
    • NEVER commit sensitive data here as it will be mirrored publicly with a clean history.
  4. Security:
    • launch-mcp.sh is ignored by git as it may contain production URLs or secrets.
    • Use .env (not tracked) for local configuration. See .env.example.
    • All unique hardware identifiers (Serial, UUID, Hostname) are anonymized before transmission.

Lifecycle & Follow-up

  • Versioning: Strictly follow Semantic Versioning 2.0.0.
  • Release Notes: Maintain a CHANGELOG.md following Keep a Changelog. Update it before every version bump.
  • Branching Model:
    • main: Reflects the production-ready state (stable).
    • feat/fix/*: Feature or fix branches merged into main via PR.
  • Bundle Size:
    • Target dist/ size under 50KB (unpacked).
    • Use npm list --prod to audit dependencies. Avoid adding heavy libraries unless essential.
  • Quality Assurance:
    • npm test: Must pass before any merge.
    • npm run lint: Zero warnings allowed in CI.
    • Prisma Integration: Ensure hardware labels match the API's diagnostic engine expectations.

Commands

npm install        # Install dependencies
npm run build      # Compile TypeScript → dist/
npm run dev        # Run without compilation (tsx)
npm run test       # Execute Vitest suite
npm run inspector  # Test tools in the browser
npm run lint       # Type checking via tsc

Architecture Technique

  • Hardware Probe: Uses systeminformation for CPU, RAM, GPU, Storage, and Screens.
  • Anonymization: Removes unique identifiers (Serial, UUID, Hostname) before transmission.
  • License: Apache 2.0 (Yamaru Project Contributors).
  • Entry point: src/index.ts with Shebang #!/usr/bin/env node.

Read the full file on GitHub · 42 lines

Changes

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.

  1. 1mo ago First seen · 42 lines · 537 tokens per session scan A 797fb8d30622

Subscribe to this mod's changes

hardware-probe GEMINI.md is an instructions file published in the GitHub repository yamaru-eu/hardware-probe (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 537 tokens to every session, about $0.0021 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-31.

Hardware and IoTgemini-cli-extensionhardware-diagnosticsllm-optimizationmcp
Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,549 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens