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/proticom/gnosys/historygit clone --depth 1 https://github.com/proticom/gnosysWrote 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/proticom/gnosys/history)<a href="https://agentmods.dev/commands/proticom/gnosys/history"><img src="https://agentmods.dev/badge/commands/proticom/gnosys/history.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 | $0.00000 | $0.00395 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
history 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 4d 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
gnosys history
Show audit history for a memory.
Usage
gnosys history mem-001
gnosys history mem-001 --limit 50 --json
Arguments
| Argument | Description |
|---|---|
memoryPath |
Memory path or ID to inspect |
Options
| Option | Description |
|---|---|
-n, --limit <number> |
Max audit entries (default 20) |
--json |
Output machine-readable JSON |
Behavior
- Opens central DB; exits with
Central DB not available.if unavailable. - Looks up memory via
getMemory(memoryPath). - Exits with
Memory not found: <memoryPath>when not found. - Fetches audit log with
getAuditLog(id, limit). - Closes DB in
finally.
Human output
No history:
Memory: Title (mem-001)
Created: 2026-01-01
Modified: 2026-02-01
No audit history recorded.
With entries:
History for Title (mem-001, 3 entries):
Created: 2026-01-01
Modified: 2026-02-01
2026-02-01 update (details)
JSON output
{
"memoryId": "mem-001",
"title": "Title",
"created": "2026-01-01",
"modified": "2026-02-01",
"entries": []
}
Validation
cd gnosys-public
npm run cli -- history --help
Related commands
gnosys audit— broader audit operations.gnosys read— read current memory content.
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.
- 4d ago First seen · 78 lines · 0 tokens per session scan A 7369c782553c
history is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 395 tokens. 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 commands, from other repositories
test-e2e
Write end-to-end tests for critical user journeys.
test-integration
Write integration tests for component boundaries.
export
Design public API exports.
newpkg
Generate new package with Nx.
cb-search
코드브레인 BM25 검색 — stale 자동 refresh.
decide
Capture a strategic decision so it never gets lost or reopened accidentally.