BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

🦀 ClawHub✦ BytesAgain

Consent

by @bytesagain1

Build cookie consent banners and track opt-in compliance status. Use when implementing GDPR consent, auditing cookies, generating privacy banners.

Versionv2.0.1

Downloads666

Installs1

#security #legal #cooking

View on ClawHub →

TERMINAL

clawhub install consent

📖 About This Skill

name: consent version: "2.0.0" author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills license: MIT-0 tags: [consent, tool, utility] description: "Build cookie consent banners and track opt-in compliance status. Use when implementing GDPR consent, auditing cookies, generating privacy banners."

Consent

Security toolkit for managing consent records — generate tokens, check strength, rotate credentials, audit logs, store and retrieve entries, manage policies, and produce compliance reports. All data stays local.

Commands

| Command | Description | |---------|-------------| | consent generate | Generate a new entry and log it | | consent check-strength | Check strength of a given input and record the result | | consent rotate | Rotate a credential or token and log the change | | consent audit | Record an audit entry for compliance tracking | | consent store | Store a value securely in the local data log | | consent retrieve | Retrieve a previously stored value | | consent expire | Mark an entry as expired | | consent policy | Record or update a policy entry | | consent report | Generate a report entry for review | | consent hash | Hash a value and store the result | | consent verify | Verify a value against stored records | | consent revoke | Revoke a previously granted consent or credential | | consent stats | Show summary statistics: entry counts, data size, first activity date | | consent export | Export all data in json, csv, or txt format | | consent search | Search across all logs for a keyword | | consent recent | Show the 20 most recent activity entries | | consent status | Health check: version, data dir, entry count, disk usage, last activity | | consent help | Show help with all available commands | | consent version | Show current version |

Command Behavior

With arguments: Each command logs the input with a timestamp to its own dedicated log file (e.g., generate.log, audit.log)

Without arguments: Each command displays the 20 most recent entries from its log file

Data Storage

Default data directory: ~/.local/share/consent/

Per-command logs: $DATA_DIR/.log (e.g., generate.log, audit.log, store.log)

History log: $DATA_DIR/history.log — master timeline of all activity

Export files: $DATA_DIR/export. — generated by the export command

All data is local plain-text. No network calls, no cloud sync.

Requirements

Bash 4+ (uses set -euo pipefail)

No external dependencies or API keys required

Works entirely offline — your data stays on your machine

When to Use

1. Tracking consent and compliance — Record who consented to what and when with store, audit, and policy for a simple compliance trail 2. Credential rotation logging — Use rotate and expire to log when credentials were changed or invalidated 3. Security auditing — Run audit entries and pull report data to review security posture over time 4. Exporting compliance data — Use export json or export csv to produce machine-readable records for external auditing tools 5. Quick lookups and verification — Search across all logs with search or verify specific entries with verify and hash

Examples

# Store a consent record
consent store "user:alice accepted terms-of-service v2.1"
Audit a policy change
consent audit "updated data retention policy to 90 days"
Generate a new token entry
consent generate "api-key-prod-2025"
Rotate a credential and log it
consent rotate "db-password-main rotated"
Check strength of a passphrase
consent check-strength "my-complex-passphrase-2025!"
Export all data as JSON
consent export json
Search across all logs
consent search "alice"
View summary statistics
consent stats
Health check
consent status
Show recent activity
consent recent

How It Works

Each domain command (generate, audit, store, etc.) maintains its own log file in the data directory. Entries are stored as timestamp|value lines. The stats command aggregates counts across all log files. The export command merges all logs into a single file in your chosen format. Every action is also recorded in history.log as a master audit trail.

Tips

Run any command without arguments to see its recent entries — great for quick review

Use consent recent to see a timeline of all activity across all commands

Pipe exports to other tools: consent export csv && cat ~/.local/share/consent/export.csv | head

Combine search with grep for complex queries: consent search "2025" | grep "policy"

Run consent help at any time for the full command reference

⚡ When to Use

Trigger	Action
2. Credential rotation logging — Use `rotate` and `expire` to log when credentials were changed or invalidated
3. Security auditing — Run `audit` entries and pull `report` data to review security posture over time
4. Exporting compliance data — Use `export json` or `export csv` to produce machine-readable records for external auditing tools
5. Quick lookups and verification — Search across all logs with `search` or verify specific entries with `verify` and `hash`

💡 Examples

# Store a consent record
consent store "user:alice accepted terms-of-service v2.1"
Audit a policy change
consent audit "updated data retention policy to 90 days"
Generate a new token entry
consent generate "api-key-prod-2025"
Rotate a credential and log it
consent rotate "db-password-main rotated"
Check strength of a passphrase
consent check-strength "my-complex-passphrase-2025!"
Export all data as JSON
consent export json
Search across all logs
consent search "alice"
View summary statistics
consent stats
Health check
consent status
Show recent activity
consent recent

📋 Tips & Best Practices

Run any command without arguments to see its recent entries — great for quick review

Use consent recent to see a timeline of all activity across all commands

Pipe exports to other tools: consent export csv && cat ~/.local/share/consent/export.csv | head

Combine search with grep for complex queries: consent search "2025" | grep "policy"

Run consent help at any time for the full command reference

Trigger	Action
2. Credential rotation logging — Use `rotate` and `expire` to log when credentials were changed or invalidated
3. Security auditing — Run `audit` entries and pull `report` data to review security posture over time
4. Exporting compliance data — Use `export json` or `export csv` to produce machine-readable records for external auditing tools
5. Quick lookups and verification — Search across all logs with `search` or verify specific entries with `verify` and `hash`