hpe-networking-mcp AGENTS.md

hpe-networking-mcp AGENTS.md is an instructions file for Codex, OpenCode from secure-ssid/hpe-networking-mcp. It costs 3,981 tokens per session, scanned A, original, MIT.

Repository instructions for working on hpe-networking-mcp, including branch names, pull-request rules, documentation updates, and pika verification. A pull request is a proposed code change submitted for review.

In plain words
What is it for?
It helps agents make changes on correctly named branches, keep project records aligned, run pika checks, and leave pull requests as drafts until checks pass.
Why use it?
It gives agents the project's working rules and prevents them from declaring work complete without running the required checks.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md; mentions Codex.

Install

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.

agentmods
npx agentmods add instructions/secure-ssid/hpe-networking-mcp/agents-md
Clone the repo
git clone --depth 1 https://github.com/secure-ssid/hpe-networking-mcp

Made for: Codex, OpenCode.

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 hpe-networking-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/secure-ssid/hpe-networking-mcp/agents-md.svg)](https://agentmods.dev/instructions/secure-ssid/hpe-networking-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/secure-ssid/hpe-networking-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/secure-ssid/hpe-networking-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,981 This file is loaded in full into every session.
When invoked 3,981 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.03981 $0.03981
Opus 5 $0.01990 $0.01990
Sonnet 5 $0.00796 $0.00796
Haiku 4.5 $0.00398 $0.00398

Measured today against content hash 4b5c1304d7a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

hpe-networking-mcp 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 today.

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.

AGENTS.md · 356 lines

How it starts

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

Agent guidance for hpe-networking-mcp

This repository is managed by pika. The contract at .project/contract.yaml declares the active profiles, the verification commands, and the repository conventions; .project/profiles.lock pins the exact profile packs in use.

Working in this repository

  • Keep the contract, the lock, and the documentation spine in sync with every change.
  • Record any deliberate deviation from a naming rule in .project/exceptions.yaml; each record needs a rule ID, a rationale, an owner, and a review condition.
  • Never bypass the verification ladder: run pika check before declaring work done.

Conventions

  • Branches: {type}/{slug} with types feat, fix, docs, refactor, chore.
  • Pull requests stay draft until checks pass.
  • Merge strategy: squash.

Driving pika

pika is a kernel that decides whether your changes are safe to keep. You propose; it verifies and commits. Nothing you assert counts as evidence — only a green verification ladder does.

Pick the command

Situation Command
Checks are failing and you want them fixed pika improve
You have a goal to implement pika work "<goal>"
A previous run was interrupted pika resume <work-id>
A run or transaction was killed and left a lock pika recover --apply
You want to know what is wrong before acting pika doctor
You do not understand a rule, gate, or error code pika explain <id>

Read the full file on GitHub · 356 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. today First seen · 356 lines · 3,981 tokens per session scan A 4b5c1304d7a3

Subscribe to this mod's changes

hpe-networking-mcp AGENTS.md is an instructions file published in the GitHub repository secure-ssid/hpe-networking-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 3,981 tokens to every session, about $0.0199 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-09-05.