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/kg-ninja/hyperxosist-agent/agents-mdgit clone --depth 1 https://github.com/KG-NINJA/HyperXosist-AgentWrote 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/kg-ninja/hyperxosist-agent/agents-md)<a href="https://agentmods.dev/instructions/kg-ninja/hyperxosist-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/kg-ninja/hyperxosist-agent/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.1 | $0.02516 | $0.02516 |
| Opus 5 | $0.01258 | $0.01258 |
| Sonnet 5 | $0.00503 | $0.00503 |
| Haiku 4.5 | $0.00252 | $0.00252 |
Grade A, and why
HyperXosist-Agent 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 yesterday.
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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — HyperXosist Agent
Instructions for any AI coding / research agent (GPT, Claude, Grok, Llama, local tool-callers).
What this is
HyperXosist builds high-signal X (Twitter) advanced search queries with noise reduction.
It does not scrape X. It produces queries + official search URLs.
Planning, filtering, and handoff are free. Automated production execution uses x402.
Default mode: universal. Grok Build is an optional powerful mode (mode: "grok").
Dual output
Core methods return structured JSON and often attach:
.markdown— human/LLM-readable summary.asMarkdown()/.asJson()helpers
Prefer JSON for tool dispatch; use markdown when pasting into a chat model.
Fast path (copy this)
A) Tool-calling agents (OpenAI / Anthropic / Grok / Llama)
// Register tools (pick one schema):
const openaiTools = HyperXosistAgent.toOpenAITools(); // Chat Completions
const anthropicTools = HyperXosistAgent.toAnthropicTools(); // Messages API
// On every tool call from the model — ONE dispatcher for all runtimes:
const out = HyperXosistAgent.dispatchToolCall(toolName, toolArgs);
// also accepts OpenAI { function: { name, arguments } } and Anthropic { name, input }
// → out.ok, out.result
B) Shell / CLI agents (no embed required)
npx hyperxosist plan "Find product feedback about <PRODUCT> for PR specs" --json
npx hyperxosist dispatch hyperxosist_plan_from_intent --args '{"intent":"Find feedback about <PRODUCT>"}' --json
npx hyperxosist tools --format openai --json
npx hyperxosist tools --format anthropic --json
npx hyperxosist keep --product <PRODUCT> --feedback '["post1","post2"]' --export-keep-only --json
npx hyperxosist handoff --product <PRODUCT> --feedback '["…"]' --json
C) Library sticky loop
// 1) Bootstrap (universal — all LLMs)
const session = HyperXosistAgent.startAgentSession({
intent: 'Find product feedback about <PRODUCT> for PR specs'
});
// 2) Plan
const plan = session.plan; // planFromIntent
const step = plan.primaryStep;
// 3) Score gate
if (!step.score.recommendPay) {
// try plan.refinements.best.input
}
// 4) Pay (x402) then search
const paid = step.paidRequest;
// POST paid.body → paid.endpoint (402 until payment proof)
// After 200: open step.searchUrl, collect candidate post texts
// 5) Self-heal if empty
// HyperXosistAgent.suggestRefinements(step.input, { tooSparse: true })
// 6) Keep-only export (any coding agent) + Signal-to-Fix
const keepOnly = HyperXosistAgent.exportKeepOnlyJson(feedback, {
productName: '<PRODUCT>',
targetArea: 'auth'
});
// → keepOnly.texts / keepOnly.signalToFixInput / keepOnly.agentPrompt
const pipeline = HyperXosistAgent.buildSignalToFixPipeline({
productName: '<PRODUCT>',
feedback: [/* posts */],
targetArea: 'auth',
context: 'optional product context'
});
// → pipeline.humanManual — show humans the free browser steps
// → pipeline.agentAuto.steps — ordered auto execution
// → pipeline.handoff.signalToFix.input → Signal-to-Fix (keep-only)
// Or:
const handoff = HyperXosistAgent.buildHandoffPackage({
productName: '<PRODUCT>',
feedback: [/* posts */],
context: 'optional product context'
});
// → handoff.signalToFix.input → Signal-to-Fix
// → handoff.agentPrompt.markdown → any coding LLM
// Optional: model-agnostic implementation prompt only
const prompt = HyperXosistAgent.buildAgentPrompt({
productName: '<PRODUCT>',
targetArea: 'auth',
feedback
});
// 7) Receipt
HyperXosistAgent.buildRunReceipt({
input: step.input,
paymentCompleted: true,
resultCount: feedback.length,
missionId: plan.missionId
});
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.
- yesterday Changed · +19 lines · +250 tokens per session c00eed042c6a
- 5d ago First seen · 233 lines · 2,266 tokens per session scan A d770c8802ad4
HyperXosist-Agent AGENTS.md is an instructions file published in the GitHub repository KG-NINJA/HyperXosist-Agent (1 stars, last pushed today), licensed MIT. It adds 2,516 tokens to every session, about $0.0126 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-31.
Other instructions, from other repositories
agoragentic-integrations AGENTS.md
AGENTS.md instructions for rhein1/agoragentic-integrations, covering agents.md, what this repository is, machine-readable index, repository structure and acp namespace rule.
agoragentic-integrations copilot-instructions.md
Copilot instructions for rhein1/agoragentic-integrations: This GitHub Copilot surface uses Agoragentic Skill Pack v2. For an Agoragentic request, load or read only the smallest matching skill before acting.
xfuel-protocol AGENTS.md
AGENTS.md instructions for XFuel-Lab/xfuel-protocol, covering xfuel — agent index, try the demo, contracts (base), repo map and commits.
licita-app AGENTS.md
AGENTS.md instructions for gastonrey/licita-app, covering licita project guidelines, product context, engineering conventions, commands and definition of done.
xenarch-mcp CLAUDE.md
Claude Code instructions for xenarch-ai/xenarch-mcp, covering xenarch-mcp, structure, stack, commands and design principle.
agoragentic-integrations GEMINI.md
Gemini CLI instructions for rhein1/agoragentic-integrations: This Gemini CLI surface uses Agoragentic Skill Pack v2. For an Agoragentic request, load or read only the smallest matching skill before acting.