Borrowing it
Nothing to install: this file belongs to openSUSE/openSUSE-packaging-skill. 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/openSUSE/openSUSE-packaging-skill/main/AGENTS.mdgit clone --depth 1 https://github.com/openSUSE/openSUSE-packaging-skillWrote 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/opensuse/opensuse-packaging-skill/agents-md)<a href="https://agentmods.dev/instructions/opensuse/opensuse-packaging-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/opensuse/opensuse-packaging-skill/agents-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/opensuse/opensuse-packaging-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/opensuse/opensuse-packaging-skill/agents-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.01682 | $0.01682 |
| Opus 5.5 | $0.00673 | $0.00673 |
| Sonnet 5.5 | $0.00336 | $0.00336 |
| Haiku 4.5 | $0.00168 | $0.00168 |
Grade A, and why
openSUSE-packaging-skill AGENTS.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 21d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing to this repository
For whoever changes this repository, human or agent. The division of labour:
README.md— for someone deciding whether to install the skill.skills/opensuse-packaging/SKILL.md— for the agent at run time. Loaded on every trigger, so it is byte-capped and routes rather than explains.AGENTS.md(this file) — conventions that would otherwise be rediscovered.
Ground rules
- Everything here is public. No personal identifiers — not yours, not anyone else's:
no forge or build-service usernames, e-mail addresses, real maintainer names, local home
paths, or build hostnames. Write generically (
<your-obs-account>, "the maintainer"). Public record ids —boo#,sr#, CVE numbers, package names — are fine.check-skills.pyenforces this; if one reaches the tip commit, amend and force-push with--force-with-leaserather than adding a scrub commit on top. - No tool or assistant attribution anywhere: no
Co-authored-by/Assisted-bytrailers, no generated-with footers, no AI authorship claims in commits, PRs, docs or code comments. - Verify against upstream, not memory. A rule worth writing down is worth checking first. Field experience is a hypothesis: most of it turns out to be already documented, already wrong, or true only of the one case that produced it.
- Conventional Commits, with the why in the body. The diff shows what changed; the message must say what it was for, and what you verified.
- Own words. Do not paste upstream documentation; state the rule and cite the source.
Token budget
SKILL.md is injected whole on every trigger, so its size is a correctness property rather
than a matter of taste. The references are read one section at a time and must stay
readable that way.
- Budgets live in
tests/test-skill-budget.shand are enforced in CI. Adding toSKILL.mdmeans trading something out of it. - State a rule once, in the file that owns the topic. Elsewhere write a pointer:
references/<file>.md "<Section>", which is literally the argument list forscripts/refsection.py.tests/test-doc-lint.shresolves every pointer, so a renamed section breaks the build instead of rotting. - Never tell anyone to read a reference whole — same lint fails on it. Detail belongs in
a reference section;
SKILL.mdgets a headline and the pointer. - Playbooks in
agents/are read by sub-agents that never seeSKILL.md. Their "read this first" list must hold exactly the sections every run of that block needs; everything conditional goes in a trigger table. Brief a sub-agent with the playbook and the sections — never with "read SKILL.md".
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.
- 21d ago Changed · +14 lines · +321 tokens per session 2601534cc550
- 22d ago Changed · +6 lines · +123 tokens per session d22d495e3bc2
- 24d ago First seen · 84 lines · 1,238 tokens per session scan A 67fa65183ad1
openSUSE-packaging-skill AGENTS.md is an instructions file published in the GitHub repository openSUSE/openSUSE-packaging-skill (8 stars, last pushed today), licensed Apache-2.0. It adds 1,682 tokens to every session, about $0.0067 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-09-22.
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).
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).