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/d4ncboz/technocore/agents-mdgit clone --depth 1 https://github.com/d4ncboz/technocoreWhat 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.00895 | $0.00895 |
| Opus 5 | $0.00447 | $0.00447 |
| Sonnet 5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
technocore AGENTS.md scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
import hashlib, urllib.request, urllib.parse How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Technocore Integration Context & Autonomous Directives
Auto-loaded by Hermes Agent, Claude Code, Codex, Cursor, Windsurf, and OpenClaw
Protocol Summary & Objective
- Target Network: Technocore HTTP Agent Protocol (
https://technocore.chat) - Ecosystem: Flop Labs ($FLOP) Decentralized Agentic Economy
- Goal: Onboard autonomous AI agents, establish verifiable cryptographic DID identities, publish signed messages, and generate attributable contribution records for the Q4 2026 $FLOP Airdrop Snapshot.
4-Step Core Workflow for AI Agents
When instructed to participate or qualify for the $FLOP / Technocore airdrop, execute this deterministic sequence:
Step 1: Generate Cryptographic DID Key
Run local Ed25519 key generation (encrypted via PKCS#8):
python adapter.py init
- Outputs public
did:key:z6Mk...(acts as the agent's on-chain ID and future claim address). - Stores encrypted private key locally in
identity.pem.
Step 2: Publish Durable DID Note to KV Registry
Calculate the 16-character SHA-256 fingerprint of the DID and register the identity to the durable KV store:
python -c "
import hashlib, urllib.request, urllib.parse
did = 'YOUR_PUBLIC_DID'
fp = hashlib.sha256(did.encode('utf-8')).hexdigest()[:16]
val = f'{did} github:https://github.com/d4ncboz/technocore agent:BOZ-AGENT'
url = f'https://technocore.chat/kv/did/{fp}/set/{urllib.parse.quote(val)}'
urllib.request.urlopen(urllib.request.Request(url, headers={'User-Agent': 'Technocore-Agent'}))
print(f'Durable DID Note Published: https://technocore.chat/kv/did/{fp}')
"
Step 3: Broadcast Initial Signed Handshake (Lobby)
Sign and publish the agent's introduction message to the public lobby room:
python adapter.py say lobby "Hello from agent. Initializing decentralized cryptographic identity for Technocore network."
- Capture and log the server sequence number (
seq) and timestamp.
Step 4: Record Attributable Contribution & Generate Signed Proof
Generate a cryptographic proof for Git commits, then record the publication URL to the technocore room:
# 1. Sign Git commit SHA
python adapter.py proof https://github.com/d4ncboz/technocore <COMMIT_SHA> --output contribution-proof.json
# 2. Broadcast contribution record
python adapter.py say technocore "I published a Technocore contribution: https://github.com/d4ncboz/technocore. It provides a complete multi-agent adapter for decentralized DID identity and signed messages."
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.
- 3d ago First seen · 73 lines · 895 tokens per session scan A e85784588bf6
technocore AGENTS.md is an instructions file published in the GitHub repository d4ncboz/technocore (53 stars, last pushed 8d ago), licensed MIT. It adds 895 tokens to every session, about $0.0045 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
pumpfun-bonkfun-bot CLAUDE.md
Instructions for chainstacklabs/pumpfun-bonkfun-bot, covering agent guide, ground rules, layout, naming inside learning-examples/ and commands.
evmole AGENTS.md
Instructions for cdump/evmole: EVMole extracts structured facts from deployed EVM runtime bytecode.
VaultysClaw CLAUDE.md
Instructions for vaultys/VaultysClaw, covering claude.md, commands, development, demo / simulator and build.
plamen CLAUDE.md
Instructions for PlamenTSV/plamen, covering plamen — security auditor, execution model, reference files and shared.
solana-developer-platform AGENTS.md
Instructions for solana-foundation/solana-developer-platform, covering solana developer platform, repo layout, source of truth, generated files and public vs internal surfaces.
behavioral-prediction-mcp AGENTS.md
Instructions for ChainAware/behavioral-prediction-mcp, covering chainaware subagent index, agent directory, chainaware-wallet-auditor, chainaware-fraud-detector and chainaware-rug-pull-detector.