Apache Axis2/C is a C framework for building and using JSON/REST and SOAP web services. It runs as an Apache httpd module, standalone server, or embedded application component, including on Android and other resource-constrained targets, and its MCP support lets AI agents call deployed services as tools.
Borrowing it
Nothing to install: this file belongs to apache/axis-axis2-c-core. 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/apache/axis-axis2-c-core/master/AGENTS.mdgit clone --depth 1 https://github.com/apache/axis-axis2-c-coreWrote 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/apache/axis-axis2-c-core/agents-md)<a href="https://agentmods.dev/instructions/apache/axis-axis2-c-core/agents-md"><img src="https://agentmods.dev/badge/instructions/apache/axis-axis2-c-core/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/apache/axis-axis2-c-core/agents-md"><img src="https://agentmods.dev/badge/instructions/apache/axis-axis2-c-core/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.01947 | $0.01947 |
| Opus 5.5 | $0.00779 | $0.00779 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (16 stars, last pushed 7d ago), licensed Apache-2.0. It adds 1,947 tokens to every session, about $0.0078 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-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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.