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 skills/sachinshelke/toolsconnector/agent_session_protocolnpx skills add sachinshelke/ToolsConnector --skill agent_session_protocolgit clone --depth 1 https://github.com/sachinshelke/ToolsConnectorWrote 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/skills/sachinshelke/toolsconnector/agent_session_protocol)<a href="https://agentmods.dev/skills/sachinshelke/toolsconnector/agent_session_protocol"><img src="https://agentmods.dev/badge/skills/sachinshelke/toolsconnector/agent_session_protocol.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.00018 | $0.00306 |
| Opus 5 | $0.00009 | $0.00153 |
| Sonnet 5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
Agent Session Protocol 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 5d 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.
What it actually says
Agent Session Protocol Skill
Overview
To function as an effective AI Agent Team (and not just isolated tools), all agents (Claude, Gemini, Cursor) must follow a strict session/handoff protocol. This ensures that the Principal Architect can pass context to the Connector Implementer without losing the thread.
Session Startup Sequence
- Read Core Instructions: Check
CLAUDE.md(orgemini.md) and/plan/brainstorm.mdto understand context. - Assess Project State: Read
.project_state.jsonto identify the current active phase and outstanding issues. - Adopt Persona: If the state mandates architecture design, assume the
principal_architectrole. If executing a tool wrapping, assume theconnector_implementerrole.
Cross-Agent Subagent Coordination
When an agent tackles a large task, they should break it down for their subagent processes:
- The Principal Architect drafts the API shape in a scratchpad or
.project_state.json. - The executing agent runs generation iteratively.
- The Health Watcher (or Verifier) validates the implementation against the rules.
Output Discipline
Before terminating a session, you MUST:
- Update
.project_state.jsonwith what was completed. - Define the remaining blockers or the next phase for the next agent session.
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.
- 5d ago First seen · 26 lines · 18 tokens per session scan A b7ee4fdc2987
Agent Session Protocol is a skill published in the GitHub repository sachinshelke/ToolsConnector (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 18 tokens to every session and 306 once invoked, about $0.0001 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 skills, from other repositories
add-test
Use when adding unit or integration tests. Provides test patterns, naming conventions, and fixtures for Python (pytest), TypeScript (vitest), Java (JUnit/Mockito), and Rust.
validate-docs
Use when reviewing or validating documentation. Checks for clarity, completeness, broken links, undefined terms, and ensures beginners can follow guides without prior knowledge of the SDK.
add-sdk-method
Use when adding a new method, function, or API endpoint to the SDK. Ensures consistent implementation across all SDKs (Python, TypeScript, Java, Rust CLI) with proper types, tests, and naming conventions.
debug-ci
Use when CI/CD pipeline fails. Provides systematic diagnosis for lint, type, test, and build failures across Python, TypeScript, Java, Rust, and n8n SDKs.
run-integration
Use when running integration tests against a real Metadata instance. Guides setup of environment variables (AISDKHOST, AISDKTOKEN) and runs tests that make actual API calls.
dignified-python
Load ONLY for Python code Use when writing, reviewing, or refactoring Python to ensure adherence to LBYL exception handling patterns, modern type syntax (list[str], str | None), pathlib operations, ABC-based interfaces, absolute imports, and explicit error boundaries at CLI level. Also provides production-tested code…