Borrowing it
Nothing to install: this file belongs to dboeckli/ai-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/dboeckli/ai-agent-skills/master/.claude/skills/project-references/SKILL.mdgit clone --depth 1 https://github.com/dboeckli/ai-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/skills/dboeckli/ai-agent-skills/project-references)<a href="https://agentmods.dev/skills/dboeckli/ai-agent-skills/project-references"><img src="https://agentmods.dev/badge/skills/dboeckli/ai-agent-skills/project-references/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/dboeckli/ai-agent-skills/project-references"><img src="https://agentmods.dev/badge/skills/dboeckli/ai-agent-skills/project-references.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
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.00116 | $0.01570 |
| Opus 5 | $0.00058 | $0.00785 |
| Sonnet 5 | $0.00023 | $0.00314 |
| Haiku 4.5 | $0.00012 | $0.00157 |
Grade A, and why
project-references 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 9d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project References
This skill manages a local mirror of your own GitHub repositories under
~/projects/referenzen/ and lets you look up conventions and implementation
patterns without guessing or reading all repos blindly.
All operations are read-only on the reference projects themselves. Only
git clone and git pull write into that directory — never edits.
Instructions
Step 1: Check whether the relevant repo is already cloned
ls ~/projects/referenzen/
If the needed repo is missing, run scripts/clone-or-update.sh owner/repo to clone it first.
Step 2: Ask the user which reference project is most relevant
Do not scan all repos blindly — that fills context. Ask: "Which of your sibling projects uses this pattern?" or list the available repos and let the user pick.
Step 3: Search targeted — file first, then grep
Use find to locate a file by name, then cat or grep to read only the relevant section. For search commands and patterns, consult references/search-patterns.md.
Step 4: Cite the source when adopting a pattern
Always state which project and file path a pattern came from before applying it:
Pattern adopted from
your-service→helm-charts/Chart.yamlline 4
Step 5: Sync only when explicitly requested
Run scripts/sync-all.sh only when the user says "sync all" or "update all references". For a single repo, prefer scripts/clone-or-update.sh.
Examples
Example 1: Looking up a Helm chart convention
User says: "How should I structure the Helm chart for this project?"
Actions:
- Run
ls ~/projects/referenzen/to see available repos - Ask: "Which sibling project should I use as reference?" — user says
your-service - Run
find ~/projects/referenzen/your-service -name "Chart.yaml"to locate it - Read the file, note the structure (apiVersion, dependencies, version pattern)
- Apply the same structure; cite: "adopted from
your-service/helm-charts/Chart.yaml"
Result: Helm chart consistent with sibling projects, traceable source cited.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 192 lines · 116 tokens per session scan A b311dd0c1f2d
project-references is a skill published in the GitHub repository dboeckli/ai-agent-skills (0 stars, last pushed 15d ago), licensed MIT. It adds 116 tokens to every session and 1,570 once invoked, about $0.0006 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.