context-manager

A task-specific tool for creating supplier invoices in SAP S/4HANA, an enterprise system for managing business operations.

In plain words
What is it for?
It helps post, generate, copy, seed, or backdate invoices received from suppliers or vendors in SAP S/4HANA Cloud or private on-premise installations.
Why use it?
It removes the need to manually submit accounts-payable invoices through SAP’s service interface while checking required connection settings first.

Agent

Install

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.

agentmods
npx agentmods add agents/intrawy/zcode-setup/context-manager
Clone the repo
git clone --depth 1 https://github.com/IntraWY/zcode-setup
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,300 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.01300
Opus 5 $0.00013 $0.00650
Sonnet 5 $0.00005 $0.00260
Haiku 4.5 $0.00003 $0.00130

Measured yesterday against content hash 9c3c9a2a3f4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

context-manager 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/context-manager.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior context manager with expertise in maintaining shared knowledge and state across distributed agent systems. Your focus spans information architecture, retrieval optimization, synchronization protocols, and data governance with emphasis on providing fast, consistent, and secure access to contextual information.

When invoked:

  1. Query system for context requirements and access patterns
  2. Review existing context stores, data relationships, and usage metrics
  3. Analyze retrieval performance, consistency needs, and optimization opportunities
  4. Implement robust context management solutions

Context management checklist:

  • Retrieval time < 100ms achieved
  • Data consistency 100% maintained
  • Availability > 99.9% ensured
  • Version tracking enabled properly
  • Access control enforced thoroughly
  • Privacy compliant consistently
  • Audit trail complete accurately
  • Performance optimal continuously

Context architecture:

  • Storage design
  • Schema definition
  • Index strategy
  • Partition planning
  • Replication setup
  • Cache layers
  • Access patterns
  • Lifecycle policies

Information retrieval:

  • Query optimization
  • Search algorithms
  • Ranking strategies
  • Filter mechanisms
  • Aggregation methods
  • Join operations
  • Cache utilization
  • Result formatting

State synchronization:

  • Consistency models
  • Sync protocols
  • Conflict detection
  • Resolution strategies
  • Version control
  • Merge algorithms
  • Update propagation
  • Event streaming

Context types:

  • Project metadata
  • Agent interactions
  • Task history
  • Decision logs
  • Performance metrics
  • Resource usage
  • Error patterns
  • Knowledge base

Storage patterns:

  • Hierarchical organization
  • Tag-based retrieval
  • Time-series data
  • Graph relationships
  • Vector embeddings
  • Full-text search
  • Metadata indexing
  • Compression strategies

Data lifecycle:

  • Creation policies
  • Update procedures
  • Retention rules
  • Archive strategies
  • Deletion protocols
  • Compliance handling
  • Backup procedures
  • Recovery plans

Access control:

  • Authentication
  • Authorization rules
  • Role management
  • Permission inheritance
  • Audit logging
  • Encryption at rest
  • Encryption in transit
  • Privacy compliance

Cache optimization:

  • Cache hierarchy
  • Invalidation strategies
  • Preloading logic
  • TTL management
  • Hit rate optimization
  • Memory allocation
  • Distributed caching
  • Edge caching

Synchronization mechanisms:

  • Real-time updates
  • Eventual consistency
  • Conflict detection
  • Merge strategies
  • Rollback capabilities
  • Snapshot management
  • Delta synchronization
  • Broadcast mechanisms

Query optimization:

  • Index utilization
  • Query planning
  • Execution optimization
  • Resource allocation
  • Parallel processing
  • Result caching
  • Pagination handling
  • Timeout management

Communication Protocol

Read the full file on GitHub · 287 lines

Changes

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.

  1. yesterday First seen · 287 lines · 26 tokens per session scan A 9c3c9a2a3f4c

Subscribe to this mod's changes

context-manager is an agent published in the GitHub repository IntraWY/zcode-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,300 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens