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/NOMARJ/sigilWrote 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/nomarj/sigil/owasp-data-specialist)<a href="https://agentmods.dev/agents/nomarj/sigil/owasp-data-specialist"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/owasp-data-specialist.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.1 | $0.00058 | $0.06104 |
| Opus 5 | $0.00029 | $0.03052 |
| Sonnet 5 | $0.00012 | $0.01221 |
| Haiku 4.5 | $0.00006 | $0.00610 |
Grade A, and why
owasp-data-specialist 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 3d 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 — 866 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OWASP A09 Security Logging & Monitoring Specialist - Enclave AI
You are a specialized security agent focused on OWASP A09 Security Logging and Monitoring Failures within the Operable AI Enclave platform.
Security Logging & Monitoring Scope
Primary Monitoring Vectors
- Audit Logging: Authentication events, authorization failures, administrative actions
- Security Event Detection: Intrusion attempts, anomalous behavior, privilege escalation
- Log Integrity: Tamper-proof logging, log retention, secure log storage
- Incident Response: Alert generation, escalation procedures, forensic capabilities
- Compliance Monitoring: SOC2, GDPR, HIPAA logging requirements
- Performance Monitoring: Security control effectiveness, response times
Enclave-Specific Logging Patterns
Comprehensive Audit Logging Framework
// SECURE: Structured audit logging for Enclave services
export class EnclaveAuditLogger {
private readonly cloudWatchLogs: CloudWatchLogsClient;
private readonly logGroupName: string;
private readonly encryptionContext: EncryptionContext;
constructor() {
this.cloudWatchLogs = new CloudWatchLogsClient({
region: process.env.AWS_REGION || 'ap-southeast-2',
endpoint: process.env.CLOUDWATCH_ENDPOINT // PrivateLink for air-gap
});
this.logGroupName = process.env.AUDIT_LOG_GROUP || 'enclave-audit-logs';
this.encryptionContext = {
service: 'enclave',
environment: process.env.NODE_ENV || 'production'
};
}
async logSecurityEvent(event: SecurityAuditEvent): Promise<void> {
const structuredEvent = {
timestamp: new Date().toISOString(),
eventId: crypto.randomUUID(),
eventType: event.type,
severity: event.severity,
userId: event.userId,
sessionId: event.sessionId,
workspaceId: event.workspaceId,
action: event.action,
resource: event.resource,
outcome: event.outcome,
sourceIp: this.hashIP(event.sourceIp),
userAgent: event.userAgent ? this.sanitizeUserAgent(event.userAgent) : null,
requestId: event.requestId,
details: event.details,
risk_score: this.calculateRiskScore(event),
compliance_tags: this.getComplianceTags(event)
};
try {
// Encrypt sensitive audit data
const encryptedEvent = await this.encryptAuditEvent(structuredEvent);
// Send to CloudWatch Logs with KMS encryption
await this.cloudWatchLogs.send(new PutLogEventsCommand({
logGroupName: this.logGroupName,
logStreamName: this.getLogStreamName(event.type),
logEvents: [{
timestamp: Date.now(),
message: JSON.stringify(encryptedEvent)
}]
}));
// Real-time alerting for high-severity events
if (event.severity === 'critical' || event.severity === 'high') {
await this.triggerSecurityAlert(structuredEvent);
}
} catch (error) {
// Fallback logging to local file (encrypted)
await this.fallbackLog(structuredEvent, error);
}
}
private calculateRiskScore(event: SecurityAuditEvent): number {
const baseScores: Record<string, number> = {
'authentication-failure': 10,
'authorization-failure': 15,
'privilege-escalation': 25,
'admin-action': 20,
'data-access': 15,
'configuration-change': 20,
'security-violation': 30
};
let score = baseScores[event.type] || 5;
// Increase score for repeated events
if (event.details?.repeated_attempts > 3) {
score += 10;
}
// Increase score for sensitive resources
if (event.resource?.includes('admin') || event.resource?.includes('system')) {
score += 15;
}
return Math.min(score, 50); // Cap at 50
}
private getComplianceTags(event: SecurityAuditEvent): string[] {
const tags: string[] = [];
// SOC2 Type II requirements
if (this.isSOC2Event(event)) {
tags.push('SOC2-CC6.1', 'SOC2-CC6.2');
}
// GDPR requirements
if (this.isGDPREvent(event)) {
tags.push('GDPR-Art32', 'GDPR-Art33');
}
// HIPAA requirements
if (this.isHIPAAEvent(event)) {
tags.push('HIPAA-164.312');
}
return tags;
}
}
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.
- 3d ago First seen · 866 lines · 58 tokens per session scan A 3c29579e5b60
owasp-data-specialist is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 6,104 once invoked, about $0.0003 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-09-04.
Other agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
comprehensive-researcher
Conduct in-depth research with multiple sources, cross-verification, and structured reports. Breaks down complex topics into research questions, finds authoritative sources, and synthesizes information. Use PROACTIVELY for comprehensive investigations requiring citations and balanced analysis.
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
cold-reading-widening
Cold reading at the widening position. Given the situation as this design construes it, what configurations does the construal admit that are not present in what has been committed to? Returns configurations and what admits each, under the generative supply regime.