Big-AGI is an open-source workspace for using multiple AI models through chat and other AI functions. It is intended for engineers, founders, researchers, and other users who want to work with AI personas, model comparisons, image generation, voice, documents, and code-related features. The catalogue entries provide commands, instructions, and a skill for working with Big-AGI.
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.
git clone --depth 1 https://github.com/enricoros/big-AGIWrote 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/enricoros/big-agi/grep-history)<a href="https://agentmods.dev/commands/enricoros/big-agi/grep-history"><img src="https://agentmods.dev/badge/commands/enricoros/big-agi/grep-history/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/enricoros/big-agi/grep-history"><img src="https://agentmods.dev/badge/commands/enricoros/big-agi/grep-history.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00571 |
| Opus 5 | $0.00009 | $0.00285 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
grep-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 13d 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
Search git history using git log -S (pickaxe) to find commits that add or remove an exact string.
This repo has 7000+ commits, so pickaxe searches can take 30-60+ seconds - this is expected.
Parameters
$0- The exact string to search for in file contents (not commit messages). Examples:getLabsSUDO,EXPERIMENT_ON_SUDO,myFunctionName$1- A commit hash or unique commit message substring to identify the start of the range. Examples:5af80b96a8,"Sudo Mode": 10-click
Example
/code:grep-history EXPERIMENT_ON_SUDO "Sudo Mode": 10-click
This searches all commits between the "Sudo Mode": 10-click commit and HEAD for any that add or remove the string EXPERIMENT_ON_SUDO in file contents.
Procedure
Step 1: Resolve the ancestor commit
If $1 looks like a commit hash (hex string), use it directly.
Otherwise, search for it by message, restricting to ancestors of HEAD:
git log --oneline --grep='$1' HEAD | head -5
This only walks commits reachable from HEAD, so every result is a guaranteed ancestor - no verification loop needed.
If multiple results, pick the oldest (last listed) since it represents the earliest matching commit. If none, report the error and stop.
Step 2: Run pickaxe search
git log -S "$0" --oneline <resolved_ancestor>..HEAD
This finds commits where the count of $0 in the codebase changes (i.e., it was added or removed).
This can be slow on 7000+ commits - wait for it.
Step 3: Check endpoints
Also check whether the string exists at HEAD and at the ancestor commit:
git grep -l "$0" HEAD 2>/dev/null || echo "(not found at HEAD)"
git grep -l "$0" <resolved_ancestor> 2>/dev/null || echo "(not found at ancestor)"
Step 4: Report
Present results concisely:
- Number of commits found (or "none")
- List of matching commits (hash + subject line)
- Whether the string exists at HEAD and/or at the ancestor
- If found, suggest next steps (e.g.,
git show <hash>to inspect specific commits)
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.
- 13d ago First seen · 63 lines · 17 tokens per session scan A e4cf5ee07c92
grep-history is a command published in the GitHub repository enricoros/big-AGI (7,120 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 571 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-30.
Other commands, from other repositories
git-commit
Based on the above changes, create a single git commit. Use the Angular commit message format：.
github-pr
Create a github pull request.
review
Review recent changes and suggest next actions. Run these steps.
flow-git
Use the @flow-git agent for git operations: $ARGUMENTS.
cl-merge
Shortcut for /consensus-loop:merge — squash-merge worktree branch.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.