npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@lumenaire/talc

v1.0.0

Published

Token-Aware Lightweight Communication — compressed encoding for agent-to-agent messages

Readme

TALC — Token-Aware Lightweight Communication

A compact encoding format for agent-to-agent messages that reduces token overhead by 38% compared to JSON — saving $100+/million messages.

License: MIT

Why TALC?

Every agent protocol today — A2A, ACP, MCP, Agora, ANP — sends verbose JSON or natural language between agents. A simple status update costs ~120 tokens in JSON-RPC format. TALC encodes the same message in ~30 tokens.

Less tokens = less compute = less energy = smaller carbon footprint.

At scale (1M agent messages/day), TALC saves an estimated ~7,400 kWh/year and $100+ per million messages on API costs.

Note: All token counts below use cl100k_base (tiktoken) — the actual tokenizer used by GPT-4, GPT-4o, and closely matching Claude's tokenizer. No estimates.

Quick Example

A security audit result in JSON-RPC (A2A-style):

{
  "jsonrpc": "2.0",
  "method": "tasks/send",
  "params": {
    "id": "task-002",
    "message": {
      "role": "assistant",
      "parts": [{
        "type": "text",
        "text": "Security audit complete. Found 3 vulnerabilities: SQL injection in login handler, exposed API key in config, missing CSRF on settings."
      }]
    }
  }
}

423 bytes, 109 tokens (cl100k_base)

The same message in TALC:

T1|T:sec-audit|S:c|F:lumen|P:0|R:3[V:sqli@login|0 V:key@config|1 V:csrf@settings|2]

119 bytes, 50 tokens — 54% fewer tokens

Installation

npm install @lumenaire/talc

Usage

import { encode, decode, encodeWithStats } from '@lumenaire/talc';

// Create a message
const msg = {
  header: { type: 'sec-audit', status: 'complete', from: 'lumen', priority: 0 },
  results: [
    { key: 'sqli', location: 'login-handler', priority: 0 },
    { key: 'key-exposed', location: 'config', priority: 1 },
    { key: 'csrf-missing', location: 'settings', priority: 2 },
  ]
};

// Encode at different compression levels
const readable = encode(msg, 0);  // L0: human-readable
const compact = encode(msg, 1);   // L1: compact (default for production)

// Decode back to structured form
const decoded = decode(compact);

// Get compression stats
const stats = encodeWithStats(msg, 1);
console.log(`Token savings: ${stats.tokenSavingsPercent}%`);
// → Token savings: 72%

Compression Levels

| Level | Name | Use Case | Typical Savings | |-------|------|----------|----------------| | L0 | Readable | Debugging, logs, human review | ~18% vs JSON | | L1 | Compact | Production agent-to-agent comms | ~38% vs JSON |

Message Types

TALC supports structured body types for common agent communication patterns:

| Type | Syntax | Use Case | |------|--------|----------| | Results | R:3[V:key@location\|priority] | Audit findings, search results, analysis | | Key-Value | K:cpu=45%\|K:mem=78% | Metrics, status data, config | | Actions | A:deploy\|TARGET:prod | Deployment requests, commands | | Diffs | D:+src/auth.ts:45-67 | Code changes, file operations | | Natural Language | NL:free text here | Fallback for unstructured content |

Header Fields

| Key | Full Name | Example | |-----|-----------|---------| | T | Type | T:sec-audit, T:status, T:deploy | | S | Status | S:complete, S:working, S:error | | F | From | F:lumen | | TO | To | TO:aire | | ID | Message ID | ID:abc123 | | RE | Reply-to | RE:xyz789 | | TS | Timestamp | TS:1711756800 | | P | Priority | P:0 (critical) to P:3 (low) |

Integration with Existing Protocols

TALC doesn't replace A2A, ACP, or MCP — it's a content encoding that sits inside them:

{
  "jsonrpc": "2.0",
  "method": "tasks/send",
  "params": {
    "message": {
      "parts": [{
        "type": "application/talc",
        "data": "T1|T:sa|S:c|R:3[V:sq@lg|0 V:ke@cf|1 V:cs@st|2]"
      }]
    }
  }
}

Benchmark Results

Tested across 6 representative message types (status updates, audit results, metrics, deployments, code reviews, multi-turn coordination):

Format              │ Tokens │ Savings vs JSON │ Savings vs NL
────────────────────┼────────┼─────────────────┼──────────────
JSON (A2A-style)    │   636  │     (baseline)  │
Natural Language    │   464  │ -27%            │   (baseline)
TALC L0 (Readable)  │   521  │ -18%            │ —
TALC L1 (Compact)   │   393  │ -38%            │ -15%

Per-message cost savings (1M messages): | Model | JSON Cost | TALC L1 Cost | Saved | |-------|-----------|-------------|-------| | GPT-4o ($2.50/1M tok) | $265 | $164 | $101 | | Claude Sonnet ($3/1M tok) | $318 | $197 | $122 |

Run the benchmark yourself:

git clone https://github.com/lumenlemons/talc.git
cd talc
npm install
npm run bench

How It Differs from Prior Art

| Project | Approach | TALC Difference | |---------|----------|-----------------| | Q-KVComm | KV cache transmission between LLMs | Requires same model architecture. TALC is model-agnostic. | | Agora | Meta-protocol negotiation in natural language | Agents negotiate at runtime. TALC is deterministic — no LLM needed to encode/decode. | | LACP | Layered security/reliability protocol | Focused on transport reliability. TALC is focused on content compression. |

Carbon Impact

If the agent ecosystem processes 1M messages/day at an average of 100 tokens each:

  • Current (JSON): ~106M tokens/day
  • With TALC L1: ~66M tokens/day
  • Saved: ~41M tokens/day → ~7,400 kWh/year
  • Cost saved: ~$101/day on GPT-4o, ~$122/day on Claude Sonnet

Scale to billions of agent messages (which is coming), and the impact becomes significant.

Roadmap

  • [x] Core spec and syntax definition
  • [x] TypeScript encoder/decoder
  • [x] Benchmark suite
  • [x] Real tokenizer benchmarks (cl100k_base via tiktoken)
  • [ ] npm package publish
  • [ ] Python encoder/decoder
  • [ ] L2 binary encoding (msgpack)
  • [ ] OpenClaw/agentic-skills integration
  • [ ] Protocol adapters (A2A content-type, MCP tool response)
  • [ ] Formal spec document (RFC-style)

Contributing

This project is in early development. We welcome contributions, ideas, and feedback.

  1. Fork the repo
  2. Create a feature branch (git checkout -b feat/my-feature)
  3. Commit with conventional commits (feat:, fix:, docs:)
  4. Open a PR

License

MIT — LumenAire Labs LLC


Built during Creative Lab at LumenAire Labs. Because agents shouldn't waste tokens talking to each other.