Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/hashicorp/agent-skills/agents-mdgit clone --depth 1 https://github.com/hashicorp/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/hashicorp/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/hashicorp/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/hashicorp/agent-skills/agents-md.svg" alt="Measured on agentmods" 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 | $0.00446 | $0.00446 |
| Opus 5 | $0.00223 | $0.00223 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
agent-skills 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 4d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This repository contains public HashiCorp Agent Skills and the Terraform and Packer product plugins that distribute them.
Canonical structure
- Put Terraform Skills in
plugins/terraform/skills/<skill-name>/. - Put Packer Skills in
plugins/packer/skills/<skill-name>/. - Keep Claude Code and Codex plugin manifests at each product root.
- Keep the Claude Code and Codex marketplaces aligned to exactly the
terraformandpackerbundles. - Keep individual Skill installation paths in
SKILLS.mdaligned with disk.
Skill requirements
- Every Skill directory must contain
SKILL.md. - Every
SKILL.mdfrontmatter must containname,description, andmetadata.lifecycle-status. - Skill names must match their directory names.
- Supported lifecycle states are
active,deprecation-candidate,deprecated, andretired. - Keep detailed material in directly linked
references/,scripts/, orassets/resources when that improves progressive disclosure.
Ownership and review
CODEOWNERS is canonical. Every Skill must have an explicit Skill-level entry
that includes @hashicorp/team-agent-skills-ecosystem. Product-aligned owners
may be added only after their participation is confirmed. The ecosystem team
owns repository conventions, evaluation integration, distribution, supported
model consistency, and final repository decisions.
Review or reevaluate a Skill whenever the Skill changes or the supported model matrix changes. Structural validation, Skill review, private Waza evaluation, CODEOWNERS review, and maintainer judgment are complementary inputs.
Contributions
The repository is in an internal-contribution-only phase. Follow
CONTRIBUTING.md and use the proposal template for a new Skill or substantial
rewrite. Do not add public evaluation fixtures or raw evaluation results.
Validation
Run these checks before proposing a change:
./scripts/validate-structure.sh
git diff --check
Run relevant example, link, installation, and harness checks for the changed surface. Never run infrastructure-creating examples against real credentials as part of repository validation.
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.
- 4d ago First seen · 56 lines · 446 tokens per session scan A ae5b2b9fc994
agent-skills AGENTS.md is an instructions file published in the GitHub repository hashicorp/agent-skills (853 stars, last pushed 7d ago), licensed MPL-2.0. It adds 446 tokens to every session, about $0.0022 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
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.