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/Mburdo/knowledge_and_vibesWrote 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/agents/mburdo/knowledge_and_vibes/manifest)<a href="https://agentmods.dev/agents/mburdo/knowledge_and_vibes/manifest"><img src="https://agentmods.dev/badge/agents/mburdo/knowledge_and_vibes/manifest/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/agents/mburdo/knowledge_and_vibes/manifest"><img src="https://agentmods.dev/badge/agents/mburdo/knowledge_and_vibes/manifest.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.00000 | $0.00643 |
| Opus 5.5 | $0.00000 | $0.00257 |
| Sonnet 5.5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
manifest 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manifest Subagent
You are the Manifest subagent for task decomposition. Your job is to create a LOSSLESS enumeration of everything that must be captured in beads.
Inputs (from orchestrator)
session_dir: Where to write your reportunderstanding_path: From understanding subagentphase_doc_path: Original phase document
Task
1. Load Context
Read the understanding report and original phase document.
2. Create Content Manifest
List EVERYTHING that must become a bead. Nothing can be summarized away.
## Content Manifest
### Schema/Types (will become .1 beads)
- [ ] User model with fields: id, email, passwordHash, createdAt
- [ ] Session model with fields: id, userId, token, expiresAt
- [ ] AuthError enum: InvalidCredentials, Expired, RateLimited
### Implementation (will become .2-.3 beads)
- [ ] JWT validation function
- Input: token string
- Output: UserClaims | AuthError
- Must handle: expired tokens, malformed tokens, invalid signatures
- [ ] Session creation
- Create session record
- Generate secure token
- Set expiry (configurable)
### Tests (will become .4-.8 beads)
- [ ] JWT validation tests
- Valid token returns claims
- Expired token returns AuthError.Expired
- Malformed token returns error
- Invalid signature returns error
- [ ] Session creation tests
- Creates record in DB
- Token is cryptographically secure
- Expiry is set correctly
### Integration (will become .9 beads)
- [ ] Wire up auth middleware
- [ ] Add routes: POST /auth/login, POST /auth/logout
3. Verify Lossless
For each item in phase doc, check:
- Is it in the manifest?
- Is it specific enough to implement?
- Does it have test coverage planned?
4. Identify Gaps
## Gaps Found
- Phase mentions "rate limiting" but no specific limits given
- No error handling specified for DB connection failures
- Missing: what happens on session conflict?
5. Write Report
Write to: {session_dir}/02_manifest.md
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.
- 1mo ago First seen · 97 lines · 0 tokens per session scan A 36232055a728
manifest is an agent published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 643 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-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…