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/apache/axis-axis2-c-core/agents-mdgit clone --depth 1 https://github.com/apache/axis-axis2-c-coreWhat 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.01947 | $0.01947 |
| Opus 5 | $0.00974 | $0.00974 |
| Sonnet 5 | $0.00389 | $0.00389 |
| Haiku 4.5 | $0.00195 | $0.00195 |
Grade A, and why
axis-axis2-c-core 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 2d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Apache Axis2/C
Security Threat Model
See SECURITY.md for the full threat model, including:
- Project description (C-based SOAP/REST/JSON web services engine)
- Roles and trust levels
- Security boundaries: what is and is not a security issue
- Attack surface by component (HTTP/2, JSON, XML parsers, memory safety)
- Memory safety profile (buffer overflows, use-after-free, format strings)
- Build-time hardening flags
- Fuzz testing and OSS-Fuzz integration
- Dependency version requirements
For detailed deployment hardening, see docs/SECURITY.md.
SOAP is the majority deployment
Recent work here targets JSON over HTTP/2, and the scan areas below reflect that. It is not the whole picture: Axis2/C is twenty years old and most installations run SOAP, so most security findings land on SOAP paths. Weight them accordingly rather than treating HTTP/2 JSON as the only live surface.
Both front ends handle SOAP. The JSON processor in apache2_worker.c is chosen
at runtime by is_json_http2_request(), not compiled in unconditionally — the
absence of #ifdef AXIS2_JSON_ENABLED around it does not mean SOAP was compiled
out.
Before testing anything SOAP, read
docs/userguide/soap-testing-guide.md.
It records the setup traps that each produce a symptom reading as "SOAP is
broken" while actually being a configuration mistake — a commented-out
transportReceiver that segfaults the standalone server, an unregistered
service whose 404 is answered by the JSON error handler, and
build_for_tests.sh running make distclean over an existing configuration.
High-Priority Scan Areas
Modern Axis2/C deployments use HTTP/2 with pure JSON — not HTTP/1.1 with SOAP/XML. The scan should weight accordingly: HTTP/2 transport, JSON processing, and the mod_axis2 Apache handler are the primary attack surface. Legacy HTTP/1.1 and XML paths are secondary.
1. HTTP/2 Transport (primary production path)
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.
- 2d ago First seen · 188 lines · 1,947 tokens per session scan A 51add2940f21
axis-axis2-c-core AGENTS.md is an instructions file published in the GitHub repository apache/axis-axis2-c-core (15 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,947 tokens to every session, about $0.0097 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
Amarok-Hider AGENTS.md
Instructions for deltazefiro/Amarok-Hider, covering amarok, project overview, build, e2e test and agent rules.
sceneview AGENTS.md
Instructions for sceneview/sceneview, covering agents.md — conventions for delegated coding agents, your role, git — you do not own it, secrets and hard technical rules.
SeekerClaw CLAUDE.md
Instructions for sepivip/SeekerClaw, covering claude.md — seekerclaw project guide, project.md — source of truth, design principle: ux first, what is this project and supported devices.
maui-labs AGENTS.md
Instructions for dotnet/maui-labs, covering agent instructions, repository overview, products, technology stack and building.
rikkahub AGENTS.md
AGENTS.md instructions for rikkahub/rikkahub, covering repository guidelines, project overview, build, test, and development commands, module structure and concepts.
AppClaw CLAUDE.md
Instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).