Borrowing it
Nothing to install: this file belongs to FilipNowakowicz/nixos-config. 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/FilipNowakowicz/nixos-config/main/.agents/skills/repo-map-query/SKILL.mdgit clone --depth 1 https://github.com/FilipNowakowicz/nixos-configWrote 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/filipnowakowicz/nixos-config/repo-map-query)<a href="https://agentmods.dev/skills/filipnowakowicz/nixos-config/repo-map-query"><img src="https://agentmods.dev/badge/skills/filipnowakowicz/nixos-config/repo-map-query/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/filipnowakowicz/nixos-config/repo-map-query"><img src="https://agentmods.dev/badge/skills/filipnowakowicz/nixos-config/repo-map-query.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.00032 | $0.00409 |
| Opus 5 | $0.00016 | $0.00204 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
repo-map-query 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 11d 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
Repo Map Query
Use .agents/repo-map/scripts/query.sh to find likely files before broad
manual exploration. This is a routing helper, not a source of truth.
When to use
- The user asks about a repo feature and the owning files are not obvious.
- You are about to open broad docs only to discover paths.
- You are about to run a wide
rgand then paste many results into context. - You need to connect task words to repo areas, hosts, checks, modules, hooks, packages, or tests.
Skip this when the exact file is already known.
Workflow
- Build 2-6 concrete query terms from the task: command names, host names, service names, checks, modules, scripts, or error words.
- Run
bash .agents/repo-map/scripts/query.sh <terms>. - Open only the top few plausible files.
- Verify the answer or edit against the real files.
Examples:
bash .agents/repo-map/scripts/query.sh merge-gate lint
bash .agents/repo-map/scripts/query.sh homeserver-gcp sops bootstrap
bash .agents/repo-map/scripts/query.sh waybar theme switch
Guardrails
- Do not treat query output as authoritative. It only says where to look first.
- Do not add repo-map output to normal summaries unless it explains a decision.
- Keep query terms specific; vague terms like
configormoduleproduce weak routing. - If the routed files don't resolve the question and broader exploration is still needed (many greps/reads across unfamiliar areas), prefer dispatching an Explore subagent and bringing back only its conclusion, rather than letting many raw search results accumulate in this session's transcript.
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.
- 11d ago First seen · 47 lines · 32 tokens per session scan A 8e77b03eb8a3
repo-map-query is a skill published in the GitHub repository FilipNowakowicz/nixos-config (5 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 409 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
agent-rig-system
A rig is a collection of riglets that provide knowledge and tools for AI agents. Rigs and riglets are packaged as Nix flake outputs, so they can both be used inside the project defining them and by other projects depending on it.
riglet-creator
Creating effective riglets means writing knowledge (SKILL.md) that agents will rely on. This guide focuses on how to write high-quality documentation for riglets, organized efficiently.
nix-module-system
Practical knowledge about lib.evalModules that's hard to find in official docs.
code-search
Fast, efficient utilities for searching code and browsing file hierarchies.
nixkits-check-updates
A maintenance workflow for checking NixKits software packages against newer upstream releases, applying updates, updating documentation, and recording the work. Nix is a package-management and build system, and a flake is its project configuration file.
write-maintenance-log
A Chinese-language workflow for writing or updating a MAINTENANCE.md software maintenance log. It records software updates and bug fixes, links entries to Git commits, and synchronizes them into five languages.