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 commands/thapaliyabikendra/ai-artifacts/wallgit clone --depth 1 https://github.com/thapaliyabikendra/ai-artifactsWrote 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/commands/thapaliyabikendra/ai-artifacts/wall)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/wall"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/wall.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.00000 | $0.02704 |
| Opus 5 | $0.00000 | $0.01352 |
| Sonnet 5 | $0.00000 | $0.00541 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
wall 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://localhost:44300/connect/token \ How it starts
The opening of the file, as written. The whole thing — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rate Limiting (Wall) Command
Implement IP-based rate limiting using AspNetCoreRateLimit and Redis distributed cache in the ABP Framework AuthServer.
Arguments: $ARGUMENTS
Pre-flight
Project: !basename $(pwd)
AuthServer Module: !find api/src -maxdepth 1 -type d -name "*AuthServer" 2>/dev/null | head -1
Required context:
- Read
CLAUDE.mdfor project conventions - Read
docs/architecture/README.mdfor project paths
Overview
This command implements distributed rate limiting to protect your AuthServer from abuse and DoS attacks by:
- Limiting requests per IP address
- Configuring endpoint-specific limits
- Using Redis for distributed caching across multiple instances
- Providing 429 (Too Many Requests) responses when limits are exceeded
Workflow
┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ 1. Verify │ → │ 2. Install │ → │ 3. Configure │ → │ 4. Update │
│ Setup │ │ Packages │ │ Module │ │ Settings │
└──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘
Execution
1. Verify AuthServer exists
# Find AuthServer project
AUTH_SERVER=$(find api/src -maxdepth 1 -type d -name "*AuthServer" 2>/dev/null | head -1)
if [ -z "$AUTH_SERVER" ]; then
echo "❌ ERROR: AuthServer project not found in api/src/"
echo "Expected: api/src/{ProjectName}.AuthServer/"
exit 1
fi
echo "✓ Found AuthServer: $AUTH_SERVER"
2. Install required NuGet packages
# Navigate to AuthServer project
cd "$AUTH_SERVER"
# Install AspNetCoreRateLimit
dotnet add package AspNetCoreRateLimit
# Install Redis support
dotnet add package AspNetCoreRateLimit.Redis
# Install StackExchange.Redis if not already present
dotnet add package StackExchange.Redis
cd ../../..
3. Configure HostModule
File: {AuthServer}/ClinicManagementSystemAuthServerModule.cs (or similar)
Add using statements at the top of the file:
using AspNetCoreRateLimit;
using StackExchange.Redis;
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 · 401 lines · 0 tokens per session scan A 782d52c15421
wall is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,704 tokens. 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 commands, from other repositories
cache-manage
Command "cache-manage" from ruvnet/RuView, covering cache-manage, usage, options, examples and view cache stats.
redis
This API allows you to manage your Managed Databases for Redis™.
index-management
Create, inspect, and drop search indexes. Wait for indexing to complete after data changes. Indexes automatically track Redis keys matching a specified prefix.
zwatch
Blocks the connection until the value at a key changes, then wakes the caller.
cloudflare-kv:test
Test KV namespace connection and operations - validates configuration, performs CRUD tests, and reports diagnostics.
v-memory-refresh
(Re)index docs/superpowers prose into the local V-memory cache so recall is current. Incremental by file hash; runs fully offline (FTS5, pure stdlib). Optionally enable the semantic lane with a one-time bootstrap. Run it after pulling new docs, or when /v:remember looks stale.