Sam Rolfe
3a8a6e98b1
The omni provider's models.json entries carried no 'cost' field, so pi's
calculateCost() returned 0 for every run and Paperclip cost events/budgets
all read $0.00 despite real spend.
- scripts/omni-pricing.mjs: pulls authoritative prices (OmniRoute /api/pricing
for deepseek/*, OpenRouter /api/v1/models for openrouter/*) and injects
{ cost: { input, output, cacheRead, cacheWrite } } USD per 1M tokens.
- Priced: deepseek-v4-flash, deepseek-v4-pro, gemini-3.1-flash-lite, gemini-2.5-flash.
- Must be re-run after every /omni sync, which rewrites models.json wholesale.
❄️ My NixOS Configuration
This directory contains the declarative configuration for my user environment, managed by Home Manager.
🛠️ How it Works (The Nix Way)
In NixOS, configuration files are managed "declaratively" rather than manually.
- The Source of Truth: Everything is defined in your
.nixfiles. - The Nix Store: When you "switch," Nix builds your files and stores them in
/nix/store/. These are immutable (read-only). - Symlinking: Home Manager creates symbolic links in your home directory (like
~/.pi/agents/settings.json) that point back to that read-only store.
✍️ How to Make Changes
Do not edit the files in your home directory. They are read-only symlinks. To change settings:
- Edit your source code: Open
home.nixinnvim. - Modify the Nix block: Locate the
home.filesection for your agents. - Apply changes:
home-manager switch
❓ Why "sudo" doesn't work
The /nix/store is mounted as read-only at the system level. This ensures your system always matches your config and allows for instant rollbacks if something breaks.
Example: Adding a local file and remote extensions
Pi Agent Configuration
To use the System Architect skills and Steel Browser extension with this project, ensure your .pi/settings.json is configured as follows:
{
"packages": [
{
"source": "/home/sam/.agents",
"extensions": [
"extensions/steel-browser/index.ts"
],
"skills": [
"skills/system-architect"
]
}
]
}
Usage
When you launch pi in this directory, it will automatically pull these assets from the Audas Media Gitea instance and activate the specialized toolset.